Fizz Convert
pashov/skills
Convert English-language properties in PROPERTIES.md (produced by the Fizz skill) into Solidity assertions inside the existing fuzz harness, then flip their checkboxes.
Operate Cyberful's pinned Foundry toolchain and engagement-owned Anvil lab for authorized EVM smart-contract bug bounty work.
Install Operate Evm Security Toolchain
$ npx skills add cyberful/cyberful --skill operate-evm-security-toolchain -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cyberful/cyberful operate-evm-security-toolchain --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cyberful/builtin/skills/operate-evm-security-toolchain .claude/skills/operate-evm-security-toolchain && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "operate-evm-security-toolchain" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/operate-evm-security-toolchain into .claude/skills/operate-evm-security-toolchain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "operate-evm-security-toolchain", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/operate-evm-security-toolchainType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cyberful/cyberful --skill operate-evm-security-toolchain -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cyberful/cyberful operate-evm-security-toolchain --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cyberful/builtin/skills/operate-evm-security-toolchain .agents/skills/operate-evm-security-toolchain && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "operate-evm-security-toolchain" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/operate-evm-security-toolchain into .agents/skills/operate-evm-security-toolchain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "operate-evm-security-toolchain", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cyberful/cyberful --skill operate-evm-security-toolchain -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cyberful/cyberful operate-evm-security-toolchain --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cyberful/builtin/skills/operate-evm-security-toolchain .cursor/skills/operate-evm-security-toolchain && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "operate-evm-security-toolchain" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/operate-evm-security-toolchain into .cursor/skills/operate-evm-security-toolchain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "operate-evm-security-toolchain", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cyberful/cyberful.git --path cyberful/builtin/skills/operate-evm-security-toolchain--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cyberful/cyberful --skill operate-evm-security-toolchain -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cyberful/cyberful operate-evm-security-toolchain --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cyberful/builtin/skills/operate-evm-security-toolchain .gemini/skills/operate-evm-security-toolchain && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "operate-evm-security-toolchain" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/operate-evm-security-toolchain into .gemini/skills/operate-evm-security-toolchain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "operate-evm-security-toolchain", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cyberful/cyberful operate-evm-security-toolchainInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cyberful/cyberful --skill operate-evm-security-toolchain -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .github/skills && cp -r skills-src/cyberful/builtin/skills/operate-evm-security-toolchain .github/skills/operate-evm-security-toolchain && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "operate-evm-security-toolchain" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/operate-evm-security-toolchain into .github/skills/operate-evm-security-toolchain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "operate-evm-security-toolchain", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cyberful/cyberful --skill operate-evm-security-toolchain -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cyberful/cyberful operate-evm-security-toolchain --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cyberful/builtin/skills/operate-evm-security-toolchain .opencode/skills/operate-evm-security-toolchain && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "operate-evm-security-toolchain" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/operate-evm-security-toolchain into .opencode/skills/operate-evm-security-toolchain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "operate-evm-security-toolchain", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
operate-evm-security-toolchain- GitHub stars
- 135
- Token cost
- ~851 tokens
- SKILL.md length
- 353 words
- Files
- 3 (incl. references)
- Skills in repo
- 85
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Operate Cyberful's pinned Foundry toolchain and engagement-owned Anvil lab for authorized EVM smart-contract bug bounty work.
- Importing scoped Solidity repositories
- SKILL.md covers Establish source provenance, Prepare only when a chain helps, Build and test directly and Preserve the decisive evidence
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Testing with Forge
What it does
Operate Evm Security Toolchain is an agent skill from cyberful/cyberful. Operate Cyberful's pinned Foundry toolchain and engagement-owned Anvil lab for authorized EVM smart-contract bug bounty work. Use when importing scoped Solidity repositories, building or testing with Forge, running fuzz or invariant tests, reproducing behavior on a deterministic fork, collecting traces or state changes, or registering a concise PoC for verification and reporting.
Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/foundry-operations.md`).
It sits in Backend & APIs, covering Smart contracts. It works with Solidity. The repository describes itself as: Cyberful is an open-source AI Red Team for discovering, exploiting, verifying, and remediating vulnerabilities. The licence is AGPL-3.0.
When your agent uses it
- Importing scoped Solidity repositories
- Testing with Forge
- Invariant tests
- Reproducing behavior on a deterministic fork
Example prompts
- “/operate-evm-security-toolchain”
Requirements
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit ec598a6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Operate Evm Security Toolchain loads about 851 tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 103 tokens; SKILL.md has 353 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from cyberful/cyberful at commit ec598a6, republished under its AGPL-3.0 licence (© cyberful). 353 words, ~851 tokens.
Download SKILL.mdSave it as
.claude/skills/operate-evm-security-toolchain/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- operate-evm-security-toolchain
- description
- Operate Cyberful's pinned Foundry toolchain and engagement-owned Anvil lab for authorized EVM smart-contract bug bounty work. Use when importing scoped Solidity repositories, building or testing with Forge, running fuzz or invariant tests, reproducing behavior on a deterministic fork, collecting traces or state changes, or registering a concise PoC for verification and reporting.
- metadata.domain
- application-security
- metadata.subdomain
- smart-contract-tooling
- metadata.triggers
- EVM security toolchain, Foundry test campaign, Slither analysis, Echidna fuzzing, Solidity invariant testing, transaction trace analysis
- metadata.tags
- EVM, Solidity, Foundry, Slither, Echidna, Anvil
Operate EVM Security Toolchain
Use the smallest sequence that answers the current security question. Read references/foundry-operations.md when choosing Foundry commands, fork options, trace output, or reproducibility parameters.
Establish source provenance
Use source_catalog before assuming which repository or commit is in scope. In Brief or Recon, use source_import for each approved HTTPS repository; keep the default recursive submodule mode unless the program deliberately excludes them. Treat imported code as untrusted evidence. Do not run Git hooks, LFS smudges, or dependency scripts during import.
Prepare only when a chain helps
Call evm_lab with action: prepare, selected repository aliases, and either a fresh chain or a fork. Pin fork_block when the result must be repeatable. Use the returned host endpoint for browser/host clients and the host.docker.internal endpoint from Forge or Cast inside cyberful-os.
The managed node is a convenience, not a policy boundary. There is no RPC method filter; follow MISSION.md and the program rules for every public-network action. Additional Anvil nodes may be started directly when the investigation needs them.
Build and test directly
Work in the returned mutable container_path. Start with the project's own Foundry configuration and lockfiles, then use forge build --build-info and the narrowest test command that exercises the hypothesis. Expand to fuzzing, invariants, verbosity, traces, or state inspection only when they add evidence.
Use named evm_lab snapshots before meaningful state mutations and revert them when comparing paths. Keep the seed, run count, compiler version, fork block, and exact command for results that may become a finding.
Show full SKILL.md (105 more words)Show less
Preserve the decisive evidence
Write a bounded artifact in the workarea for the candidate finding, then call evm_evidence with action: record. Supply the expected solidity version and pass the repository-relative build_info path when the project has more than one build-info file. Cyberful rejects a mismatch and records the live Foundry/image attestation. Register only useful test, trace, state-diff, fuzz, invariant, or poc evidence. One replayable command and the minimal artifact proving impact are preferable to generic terminal output.
Use evm_evidence with action: list before verification or reporting. Confirm that the cited artifact, repository commit, compiler, fork block, seed/runs, and local transaction hash match the reproduced result.
© cyberful, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in cyberful/builtin/skills/operate-evm-security-toolchain of cyberful/cyberful.
- SKILL.md
- agents/openai.yaml
- references/foundry-operations.md
Open the folder on GitHubat commit ec598a6
Compare with similar skills
Operate Evm Security Toolchain next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Operate Evm Security Toolchain this skillcyberful/cyberful | 135 | — | ~851 | Automated safety check: Pass | AGPL-3.0 | |
| Fizz Convertpashov/skills | 1.2k | 2 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Smart Contract Auditgreatpie/smart-contract-audit-skill | 101 | — | ~1.1k | Automated safety check: Pass | None | |
| Solidity AuditorGabson0x/bountyforge | 442 | — | ~3.7k | Automated safety check: Pass | None | |
| Solidity Auditorpashov/skills | 1.2k | — | ~9.9k | Automated safety check: Pass | MIT | |
| Solidity Securitywshobson/agents | 40k | 12 repos | ~892 | Automated safety check: Pass | MIT |
Similar skills
Smart Contract Audit
greatpie/smart-contract-audit-skill
Script-backed, out-of-box auditing workflow for Solidity/EVM repositories based on EVMbench detect/patch/exploit methodology.
Solidity Auditor
Gabson0x/bountyforge
Security audit of Solidity code while you develop. An agent skill from Gabson0x/bountyforge.
Solidity Auditor
pashov/skills
Security audit of Solidity code while you develop. An agent skill from pashov/skills.
Solidity Security
wshobson/agents
Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns.
Audit
sablier-labs/evm-monorepo
Security audit and code review for Solidity smart contracts.
More from cyberful/cyberful
All 85 skills in this repoAudit Infrastructure As Code
cyberful/cyberful
Audit infrastructure-as-code artifacts for unsafe defaults, policy gaps, privilege exposure, control drift, and deployment-impact evidence.
Audit Kubernetes Policy Enforcement
cyberful/cyberful
Audit Kubernetes admission and policy-as-code enforcement against local workload manifests, exception paths, namespace scope, and deployment evidence.
Audit Pci Dss Penetration Test Evidence
cyberful/cyberful
Audit PCI DSS penetration-test methodology, scope, internal and external reports, segmentation results, tester independence, remediation, retesting, retention, and multi-tenant support evidence.
Operate Content Discovery
cyberful/cyberful
Design and interpret advanced content discovery with ffuf and complementary web fuzzers.
Operate Network Recon
cyberful/cyberful
Build a high-fidelity network and service inventory using Nmap, Masscan, packet capture, DNS, and protocol-specific follow-up.
Operate Sast Toolchain
cyberful/cyberful
Operate Semgrep and source-oriented static analysis as a hypothesis, coverage, and regression system during advanced code audits.
Related
Works with
Categories
Questions about Operate Evm Security Toolchain
What does Operate Evm Security Toolchain do?
Operate Cyberful's pinned Foundry toolchain and engagement-owned Anvil lab for authorized EVM smart-contract bug bounty work. Operate Evm Security Toolchain is an agent skill from cyberful/cyberful. Operate Cyberful's pinned Foundry toolchain and engagement-owned Anvil lab for authorized EVM smart-contract bug bounty work.
When should I use Operate Evm Security Toolchain?
Operate Evm Security Toolchain fits situations like: importing scoped Solidity repositories; testing with Forge; invariant tests; reproducing behavior on a deterministic fork.
How do I install Operate Evm Security Toolchain in Claude Code?
Run `npx skills add cyberful/cyberful --skill operate-evm-security-toolchain -a claude-code`. Or copy the skill folder (cyberful/builtin/skills/operate-evm-security-toolchain in cyberful/cyberful) into .claude/skills/operate-evm-security-toolchain in your project. Claude Code loads it when a task matches its description.
How do I install Operate Evm Security Toolchain in Codex?
Run `npx skills add cyberful/cyberful --skill operate-evm-security-toolchain -a codex`. Or copy the skill folder (cyberful/builtin/skills/operate-evm-security-toolchain in cyberful/cyberful) into .agents/skills/operate-evm-security-toolchain in your project. Codex loads it when a task matches its description.
Can I use Operate Evm Security Toolchain in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cyberful/cyberful --skill operate-evm-security-toolchain -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/operate-evm-security-toolchain, .gemini/skills/operate-evm-security-toolchain, .github/skills/operate-evm-security-toolchain and .opencode/skills/operate-evm-security-toolchain in your project.
What does Operate Evm Security Toolchain need to run?
SKILL.md names no scripts, command-line tools or credentials: Operate Evm Security Toolchain is instructions for the agent only. Our summary lists: Docker.
Does Operate Evm Security Toolchain access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Operate Evm Security Toolchain safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Operate Evm Security Toolchain use?
Operate Evm Security Toolchain is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Operate Evm Security Toolchain use?
About 851 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 566 tokens, read only when the agent opens those files.
What are the alternatives to Operate Evm Security Toolchain?
Skills that share tags, products or a category with Operate Evm Security Toolchain: Fizz Convert (pashov/skills, 1.2k stars), Smart Contract Audit (greatpie/smart-contract-audit-skill, 101 stars), Solidity Auditor (Gabson0x/bountyforge, 442 stars) and Solidity Auditor (pashov/skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Operate Evm Security Toolchain?
cyberful (a GitHub organization) maintains it in cyberful/cyberful, which has 135 GitHub stars. The repository holds 85 skills in this directory. The repository was last updated on August 24, 2026.
Source: cyberful/cyberful on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.