Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add OutlineDriven/outline-driven-development --skill burp-search-commandgit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/outlinedriven/outline-driven-development/burp-search-command)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/burp-search-command"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/burp-search-command.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high YARA Match · line 29 YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00050 | $0.01108 |
| Opus 5 | $0.00025 | $0.00554 |
| Sonnet 5 | $0.00010 | $0.00222 |
| Haiku 4.5 | $0.00005 | $0.00111 |
Grade A, and why
burp-search-command scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Burp search command
Contract
| Field | Bound contract |
|---|---|
| Trigger | A human explicitly invokes the Burp search command with a required .burp file and optional parser operation. |
| Authority | Read-only. No file, VCS, credential, paid, published, deployed, or remote mutation. The command only reads the specified .burp project file through the Burp Suite parser. |
| Side effect | Local read of the command-selected .burp project through the Burp parser wrapper. No project file is modified; output is written to stdout only. |
| Done | A valid project path and optional operation are passed to the full bounded Burp parser workflow and its JSON result is returned. |
Inputs
- Burp project file (required): Path to a
.burpproject file. Must exist on the local filesystem. - Operation (optional, at least one expected for useful output): One of:
auditItems: extract all security audit findings.proxyHistory: dump all proxy history entries.siteMap: dump all site map entries.responseHeader='regex': search response headers with a regex.responseBody='regex': search response bodies with a regex.- Sub-component filters appended with dots:
proxyHistory.request.headers,proxyHistory.request.body,proxyHistory.response.headers,proxyHistory.response.body, and the same patterns forsiteMap.*.
Environment variables (optional overrides):
BURP_JAVA: path to the Java executable. Defaults to the Burp Suite Professional bundled JRE (/Applications/Burp Suite Professional.app/Contents/Resources/jre.bundle/Contents/Home/bin/javaon macOS,/opt/BurpSuiteProfessional/jre/bin/javaon Linux).BURP_JAR: path toburpsuite_pro.jar. Defaults to/Applications/Burp Suite Professional.app/Contents/Resources/app/burpsuite_pro.jaron macOS,/opt/BurpSuiteProfessional/burpsuite_pro.jaron Linux.
Prerequisites: Burp Suite Professional with the burpsuite-project-file-parser extension installed.
Procedure
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 57 lines · 50 tokens per session scan A d92eb899a235
burp-search-command is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 2d ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,108 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
duet
Use when the user invokes /duet, says "pair with me", or faces aesthetic, architectural, or irreversible decisions.
goal-prompt-drafting
Use when asked to draft copy-ready /goal objectives for long-running agents; returns one normalized one-line objective with measurable end state, grounded proof, easy-out invariants, a stop clause, and a Missing list. Not for source or remote-system changes.
handoff-prompt
Use when the user asks for a handoff, delegation, or clipboard-ready prompt for another agent: a standalone path-free prompt copied to the clipboard, confirmed by title. Not for session-snapshot briefs — use handoff; never remote, credential, publish, deploy, or irreversible.
publish-branch
Use when asked to publish the checked-out branch: commit and push it on whatever branch it is, the default branch included. Not for creating branches, PRs, force pushes, or pushing any other branch; when the request excludes the default branch, use commit-push-current.
drill
Use when a concept needs practising rather than explaining: run a scaffolded exercise from worked example to independent problem, quiz the learner, run spaced recall over what they cleared, or probe for the gaps blocking what they want next. For explanation, use explain-concept; for an end-to-end build, use capstone.