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 agents/policyengine/policyengine-claude/report-loggergit clone --depth 1 https://github.com/PolicyEngine/policyengine-claudeWhat 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.00074 | $0.03302 |
| Opus 5 | $0.00037 | $0.01651 |
| Sonnet 5 | $0.00015 | $0.00660 |
| Haiku 4.5 | $0.00007 | $0.00330 |
Grade A, and why
report-logger 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 2d 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report Logger
Final stage of /analyze-policy. Takes the assembled report and the verdict, and writes it to the right destinations.
Inputs
report_path: path to the final markdown report (e.g.,/tmp/analyze-policy-{policy_id}.md)frontmatter: structured metadata (policy_id, verdict, jurisdiction, anchor_url, tags, etc.)log_to: list of destinations (auto-derived from verdict unless overridden by--log-to)no_log: if true, skip logging entirelycommand_args: the original$ARGUMENTSpassed to /analyze-policy (for traceability)
Routing — runtime prompt, context-aware
Destinations depend on where the analyst is working and what the analysis is for. Rather than a single auto-route, the agent computes a context-aware destination shortlist and prompts the analyst to pick.
If --log-to was explicitly passed: skip the prompt, use the list verbatim.
If --no-log: skip the prompt, write nothing.
If --auto-confirm AND no --log-to: use the verdict default (local archive only) without prompting.
Otherwise:
Step 1: Detect context
Run these checks in parallel (cheap):
# Current repo
git rev-parse --show-toplevel 2>/dev/null # e.g., /Users/pavel/policyengine-app-v2
gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null # e.g., PolicyEngine/policyengine-app-v2
# Is there a posts/articles directory? (policyengine-app-v2 shape)
test -d app/src/data/posts/articles && echo "HAS_POSTS_DIR"
# Is there an analyses/ directory? (this repo's shape)
test -d analyses && echo "HAS_ANALYSES_DIR"
# Country from --country flag or from the reform's jurisdiction
echo "$COUNTRY"
Step 2: Build the shortlist
Always include:
- Local archive (path per resolution order in next section)
- Skip / no-log (cancel destination)
Append context-specific options:
| Context | Add this option |
|---|---|
Inside policyengine-app-v2 repo (HAS_POSTS_DIR) |
"Save as draft research post: app/src/data/posts/articles/{slug}.md + update app/src/data/posts/posts.json" |
Inside policyengine-skills or any repo with analyses/ |
"Just the archive in analyses/" (already covered by local archive but make the path explicit) |
Verdict is INVESTIGATE |
"Open GitHub issue in the country's data repo (us → PolicyEngine/microcosm; other countries → policyengine-{country}-data) — calibration hypothesis" |
Verdict is structural |
"Open GitHub issue in PolicyEngine/policyengine-{country} (model-change estimate)" |
Verdict is PASS* AND inside policyengine-app-v2 |
"Open draft PR to policyengine-app-v2 with the post body" |
| Always | "Custom path / repo — type a destination spec" |
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.
- 2d ago First seen · 326 lines · 74 tokens per session scan A c59d63b7656a
report-logger is an agent published in the GitHub repository PolicyEngine/policyengine-claude (31 stars, last pushed 8d ago), licensed MIT. It adds 74 tokens to every session and 3,302 once invoked, about $0.0004 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 agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
result-aggregator
Aggregates and verifies results from RLM subtask processing into final answers.
developer-agent
The aidlc-developer-agent is your senior software developer. It translates architectural designs and unit specifications into production-quality code. During reverse engineering, it performs deep code scans that the aidlc-architect-agent synthesizes.