quickstart
Skill25 starsChanged 4 months agoApache-2.0View on GitHub
The front door for this repo. With no argument: a 30-second intro, then an offer to walk you through your first run on the canary target. With a question: answers it from this repo's own docs and source, cites where it looked, and hands you the next command. Use for "how do I…", "why does…", "where is…", "can this…", or just "/quickstart" to get oriented.
10 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- dvy1987/agent-loomtheir own version, first seen Nov 15, 2026
- Talkif-ai/skillstheir own version, first seen Nov 13, 2026
- NangoHQ/skillstheir own version, first seen Nov 4, 2026
- databricks/app-templatestheir own version, first seen Oct 8, 2026
- apache/pinottheir own version, first seen Oct 8, 2026
- joris887/exosuittheir own version, first seen Aug 20, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- anthropics/defending-code-reference-harness★ 7.5k82% same
Wrote their own version · 9
- apache/pinot★ 6.2ksame name
- databricks/app-templates★ 222same name
- joris887/exosuit★ 9same name
- dvy1987/agent-loom★ 4same name
- NangoHQ/skills★ 3same name
- IdkwhatImD0ing/hackathonstarterkit★ 2same name
- JustineDevs/premortem★ 2same name
- brainsparker/skills★ 1same name
- Talkif-ai/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- customizeSkill
- patchSkill
- quickstartSkill
- sast-drivenSkill
- sast-prioritiseSkill
- threat-modelSkill
- triageSkill
- variant-scanSkill
- verifySkill
- vuln-scanSkill
- customizeSkill
- patchSkill
- sast-drivenSkill
- sast-prioritiseSkill
- threat-modelSkill
- triageSkill
- variant-scanSkill
- verifySkill
- vuln-scanSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Non-empty → Help mode: Treat $ARGUMENTS as the operator's question.
- Distinctive: line 30
Keep it short and a little warm.
- Distinctive: line 98
Don't answer from general knowledge when the repo has a specific answer.
- Distinctive: line 130
If the question is ambiguous, ask one clarifying question.
- Very specific: line 134
Never fabricate CLI flags or file paths.
- Distinctive: line 136
If the repo doesn't answer the question, say so plainly and suggest the operator open a GitHub issue on this repo.
- Distinctive: line 138
Keep the Q&A dry and cited.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/quickstart
Two modes, picked by whether $ARGUMENTS is empty.
- Empty → Intro mode. Short orientation, then offer the guided first run.
- Non-empty → Help mode. Treat
$ARGUMENTSas the operator's question.
Intro mode
Keep it short and a little warm; this is the first thing a new operator sees.
Say roughly:
Welcome! This repo takes you from finding your first vulnerability to patching at scale, using a set of Claude Code skills and an autonomous pipeline. It's rust-first — the headline is the
rustprofile (Miri/panic/hang detectors + cargo-fuzz, capability-routed fuzzing, find→fuzz reattack, the scorecard) — with a fully retained C/C++ + ASan base. Two ways in: interactive skills (no setup, safe, start here) and the autonomous pipeline (Docker, scales to hundreds of parallel agents).The ramp-up:
| Day 1 | Threat-model + first static scan + triage | | Day 2 | Run the reference pipeline (rust-canary; cpp base also available) | | Day 3-4 | Customize it for your stack | | Week 2 | Autonomous scanning, triage, and patching |
Day-1 goal: threat-model, scan, and triage the bundled canary target. Most teams get there before lunch.
Remind them to export CLAUDE_CODE_SUBAGENT_MODEL=<model-id> so subagents
use the same model as the session.
Then AskUserQuestion with three options:
- Walk me through Day 1 on the canary (~10 min) → run "Guided first run" below.
- I have a question → ask what it is, then switch to Help mode.
- I'll read the README → point at
README.mdStep 1 and stop.
Guided first run
Runs the three Step-1 skills on targets/rust-canary (the rust-first
default), pausing after each to show what landed on disk. These only
read/write files in the repo; no sandbox needed. Prefer rust-canary; offer
targets/canary (the cpp base) if the operator's stack is C/C++.
/threat-model bootstrap targets/rust-canaryvia Task. When done, opentargets/rust-canary/THREAT_MODEL.md, show the focus areas, explain in 2-3 sentences how this steers the scan./vuln-scan targets/rust-canary/crate --extra profiles/rust/scan-extras.txtvia Task (the canonical rust invocation —scan-extras.txtadds the Rust vuln classes to the brief). When done, opentargets/rust-canary/crate/VULN-FINDINGS.md, summarize the count and top 2-3 findings, point atVULN-FINDINGS.json./triage targets/rust-canary/crate/VULN-FINDINGS.json --repo targets/rust-canary/crate --fp-rules profiles/rust/fp-rules.txtvia Task (fp-rules.txtcarries the R1–R11 rust precedents). When done, openTRIAGE.md, explain what changed vs. raw findings (verified, deduped, re-ranked).For the cpp base instead, drop the
--extra/--fp-rulesfiles and point attargets/canary.
Pause for the operator between each (AskUserQuestion); don't barrel through.
Close with a one-line recap of the three artifacts on disk, then point at
README Step 2 for the execution-verified pipeline. Never run vuln-pipeline
or anything that executes target code here; that's Step 2 and needs
Docker + a sandbox.
Help mode
Answer the operator's question using this repo as ground truth: README,
docs/*.md, harness/*.py, targets/*/config.yaml, .claude/skills/*.
Don't answer from general knowledge when the repo has a specific answer.
Routing map
| If the question is about… | Read first | Then offer |
| running the pipeline | docs/pipeline.md, README Step 2 | the recon / run command |
| SAST / running the scanners / rule packs / CodeQL | docs/sast-layer.md, docker/sast/README.md | /sast-driven <crate>, then /sast-prioritise |
| too many findings, triage | docs/triage.md | /triage <path> |
| the rust profile, rust-canary | profiles/rust/README.md | run rust-canary |
| the android-app profile, APK, decompiled DEX, MASVS/MASTG | profiles/android-app/README.md, docs/profiles/android/DECISIONS.md | run android-canary; /vuln-scan <decompiled> --extra profiles/android-app/scan-extras.txt, /triage … --fp-rules profiles/android-app/fp-rules.txt |
| capability routing, which checks run | profiles/rust/capabilities.md / profiles/android-app/capabilities.md | cite the capability→check map |
| reattack, find→fuzz, promoting findings | profiles/rust/find-to-fuzz.md | vuln-pipeline reattack <results> |
| scorecard, discipline gate, union-of-N | profiles/rust/README.md, README Step 2 | vuln-pipeline scorecard <results> |
| porting, adding a profile, Java/Go/etc. | docs/customizing.md, README Step 3 | /customize |
| safety, sandbox, Docker | docs/security.md | cite; no action |
| rate limits, 429, token budget | docs/pipeline.md: Rate limits, docs/troubleshooting.md#rate-limits | cite the numbers |
| duplicates, dedup | docs/troubleshooting.md#duplicate-findings | known_bugs: hint |
| CLI flags, "what does --X do" | harness/cli.py (grep the argparse) | exact flag + example |
| which model, subagent pinning | docs/troubleshooting.md: Subagents | the export line |
| best practices, prompting | docs/security.md, docs/pipeline.md | cite the principle |
| "how do I start" | README Step 1 | offer Guided first run |
| patching, fix, diff, re-attack | docs/patching.md, README Step 4 | /patch <input> |
| binary, pentest, other domains | docs/customizing.md, docs/extending.md | cite section |
| anything else | README Table of contents | best-match doc |
Answer format
- Direct answer in 2-5 sentences.
> source:the file(s) and section you used.- Next action: one copy-pasteable command or skill invocation, if one applies. If none does, say so.
- If the question is ambiguous, ask one clarifying question; don't guess.
Constraints
- Never fabricate CLI flags or file paths. If unsure,
Grepfor it inharness/cli.pyor the target configs and quote what you find. - If the repo doesn't answer the question, say so plainly and suggest the operator open a GitHub issue on this repo.
- Keep the Q&A dry and cited. Save the warmth for Intro mode.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

