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/rojim666/SztuCodeWrote 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/rojim666/sztucode/cli)<a href="https://agentmods.dev/agents/rojim666/sztucode/cli"><img src="https://agentmods.dev/badge/agents/rojim666/sztucode/cli/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/rojim666/sztucode/cli"><img src="https://agentmods.dev/badge/agents/rojim666/sztucode/cli.svg" alt="Reviewed on agentmods" width="80" 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.00004 | $0.00124 |
| Opus 5.5 | $0.00002 | $0.00050 |
| Sonnet 5.5 | $0.00001 | $0.00025 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
cli 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 1mo 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.
What it actually says
cli-agent-prompt
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.
- 1mo ago First seen · 7 lines · 4 tokens per session scan A e2e9ecd0ad21
cli is an agent published in the GitHub repository rojim666/SztuCode (109 stars, last pushed 4d ago), licensed MIT. It adds 4 tokens to every session and 124 once invoked, about $0.0000 per session on Opus 5.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-12.
Other agents, from other repositories
mach12:code-architect
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences.
scramjet:command-reviewer
Use when a proposed or authored Scramjet command change warrants independent holistic review.
scramjet:independent-command-assessor
Use when another reviewer has produced command findings that require fresh independent adjudication before fixes are authorized.
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.
forge-speccer-validator
Pre-planning path-validation gate. Scans a spec file for path tokens inside code fences or backticks, checks each against the target repo, and returns REPLANNEEDED with (spec-line, missing-path) pairs when any are missing. Invoked automatically by /forge plan before forge-planner.
forge-speccer
Writes specifications with R-numbered requirements and testable acceptance criteria from brainstorm output. Use during /forge brainstorm to generate spec files.