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 agentmods add commands/transilienceai/communitytools/reportgit clone --depth 1 https://github.com/transilienceai/communitytoolsWrote 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/commands/transilienceai/communitytools/report)<a href="https://agentmods.dev/commands/transilienceai/communitytools/report"><img src="https://agentmods.dev/badge/commands/transilienceai/communitytools/report.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 | $0.00037 | $0.01238 |
| Opus 5 | $0.00018 | $0.00619 |
| Sonnet 5 | $0.00007 | $0.00248 |
| Haiku 4.5 | $0.00004 | $0.00124 |
Grade A, and why
report 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/report — Render deliverables
No arguments. Operates on the most recent engagement.
Implementation boundary: this command is a reference workflow. The scripts it names are not shipped in communitytools; confirm an accessible compatible runtime before execution. See ../IMPLEMENTATION_STATUS.md.
What to do
Step 1 — Preflight
- Check
findings.final.jsonlexists. If not, error: "run /launch first". - Check
feedback.jsonlexists and has at least one"decision":"approve"entry.- If missing AND the operator has explicitly requested the report without running
/review(e.g. asked for "the report now" / "skip review, render"), synthesize a batch-approvefeedback.jsonl— one entry per finding withdecision: "approve",decided_by: <engagement.lead_assessor>,mode: "batch-approve-at-report", andreasonnoting that interactive review was skipped by operator choice. This preserves the audit trail (the mode field makes the path explicit) and satisfies the/reportgate. Print a one-line notice in chat so the operator sees it: "Synthesized batch-approve feedback.jsonl; audit trail recordsmode: batch-approve-at-report." - If missing AND the operator did NOT ask to skip
/review, error: "run /review and approve at least one finding first".
- If missing AND the operator has explicitly requested the report without running
- Verify
scoping-questionnaire.yamlhas non-emptyengagement.client,engagement.lead_assessor, andregulatory_overlay. If any are empty, ASK the operator to fill them before rendering — these fields appear on the PDF cover page and in the appendix.
Step 2 — Render deliverables
Run:
python3.11 scripts/render-pdf.py <engagement-dir>
python3.11 scripts/render-xlsx.py <engagement-dir>
These write:
deliverables/report.pdf(10-section canonical audit layout; record the actual rendered page count)deliverables/remediation-tracker.xlsx(current base renderer: 28-column Findings & Action Plan plus 5 supporting tabs)deliverables/manifest.json(chain-of-custody: tool/skill versions + input SHA256s + engagement metadata)
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 · 79 lines · 37 tokens per session scan A d370ca9bc19e
report is a command published in the GitHub repository transilienceai/communitytools (507 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,238 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-30.
Other commands, from other repositories
brand-generate
Generate an on-brand document from a saved Brand Profile.
develop-image-prompt.eval
Generates a detailed image generation prompt from a document or content description. Good output: a prompt that is specific, visual, non-abstract, includes style/composition/lighting guidance, and is calibrated to the specified dimensions and style options.
extract-pdf-features
Extract per-player prospect features from cached PDF text (uses your Claude subscription, not the API).
research
Document codebase as-is with thoughts directory for historical context.
slides
Regenerate the presentation slides using Marp.
aja-generate-cv-pdf
Render a CV HTML file to PDF using Chrome headless.