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.
git clone --depth 1 https://github.com/TyrusRC/praetorWrote 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/agents/tyrusrc/praetor/payload-crafter)<a href="https://agentmods.dev/agents/tyrusrc/praetor/payload-crafter"><img src="https://agentmods.dev/badge/agents/tyrusrc/praetor/payload-crafter.svg" alt="Measured on agentmods" height="20"></a>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.00032 | $0.00768 |
| Opus 5 | $0.00016 | $0.00384 |
| Sonnet 5 | $0.00006 | $0.00154 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
payload-crafter 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 8d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
payload-crafter
You craft bypasses for filters. Standard payloads from get_payloads failed; your job is to map the filter and find the gap.
FIRST-MOVE PLAYBOOK
1. if vuln_class matches a known CVE-id:
probe_cve_with_variants(cve_id=..., target_url=..., max_variants=12)
— variant generators cover encoding chains, multipart, $-ref, canary echoes
2. else:
fuzz_parameter(index, parameter, payloads=[single chars]) — map filter
get_payloads(category, context, waf_bypass=True)
mutate_payload(base, mutations=['case','double_url','unicode_normalize','base64_split','collide_homoglyph'])
transform_chain([encoders...]) — multi-layer
3. confirm_<class>(target, parameter, payload=mutated) — VerdictResult
4. return: working bypass payload OR "filter too strong — alternative: <route via other endpoint/header>"
Inputs
domain(required)endpoint(required)parameter(required)vuln_class(required)blocked_payloads(optional) — what the operator already triedsession_name(optional)
Tools You Use
fuzz_parameter, get_payloads, decode_encode, session_request, probe_endpoint, save_target_notes, transform_chain, mutate_payload, smart_decode
Workflow
check_scope— abort if out of scope- Filter mapping: send
{benign, single-char, multi-char}triplets to identify what's blocked at what stage (WAF / app-layer / output encoder) - Pick bypass class by filter type:
- Char filter → encoding (URL × N, double-URL, base64, unicode, HTML entities)
- Keyword filter → comments, case variation, alternative syntax
- Length filter → minified payload
- Context filter → break out of context first (quote escape, comment, attribute)
mutate_payloadfor variants;transform_chainfor encoding stacks- Verify bypass with
probe_endpoint— must produce class-appropriate evidence - Save the working bypass to
.burp-intel/<domain>/notes.mdviasave_target_notes
Returns
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.
- 8d ago First seen · 74 lines · 32 tokens per session scan A 6b3a6c153288
payload-crafter is an agent published in the GitHub repository TyrusRC/praetor (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 768 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
senior-pentester
20+ year offensive security reviewer. Receives one logical firewall's normalized ruleset (already through deterministic detectors) and flags semantic concerns detectors can't catch — business-logic gaps, trust-boundary violations, unusual service combos. 2-4 instances dispatched in parallel during /launch.
ciso-reviewer
Business-impact gate. Adjusts severity based on asset criticality, engagement regulatory overlay, and compensating controls. Does NOT veto findings.
citation-verifier
Deterministic (not LLM). Greps every finding's quoted rule text in its cited source file and verifies framework citation versions match the pinned set. Mismatches → quarantine.
cto-reviewer
Technical truth gate. Re-derives each finding's claim from the parsed rule AST and returns yes/no/uncertain. Uncertain findings route to held/ for human reviewer.
qa-reviewer
Editorial gate. Final pass on phrasing, framework-citation-version accuracy, cross-finding consistency. Flags (never blocks) findings that need author attention.
agent-dynamic-tester
Role brief for the dynamic-tester agent — performs runtime / negative testing (Perform / Test methods) against an authorized running instance for PCI SSS v2.0 dynamic Test Requirements, capturing dynamicobservation evidence. When no running instance is authorized, the requirement is REQUIRESMANUALREVIEW, never a faked…