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/daddia/claude-for-strategyWrote 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/daddia/claude-for-strategy/cadence-reporter)<a href="https://agentmods.dev/agents/daddia/claude-for-strategy/cadence-reporter"><img src="https://agentmods.dev/badge/agents/daddia/claude-for-strategy/cadence-reporter/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/daddia/claude-for-strategy/cadence-reporter"><img src="https://agentmods.dev/badge/agents/daddia/claude-for-strategy/cadence-reporter.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.00044 | $0.00715 |
| Opus 5 | $0.00022 | $0.00358 |
| Sonnet 5 | $0.00009 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
cadence-reporter 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cadence Reporter
Runs monthly by default (09:00 on the 1st) — override the schedule to match the reporting cadence recorded in the practice profile (~/.claude/plugins/config/claude-for-strategy/performance/CLAUDE.md) if it differs (e.g. weekly Monday, quarterly on the 1st of Jan/Apr/Jul/Oct).
What it does
-
Reads the practice profile for reporting cadence, audience, North Star metric(s), metric taxonomy, and where period data lives (tracker path,
~~spreadsheet,~~observability). -
Determines whether today is a reporting day for the recorded cadence. When the schedule fires on a non-reporting day (because the cron is a default), exit quietly — no post, no file. When today matches the cadence, proceed.
-
Gathers period metrics for the reporting window just closed:
- Manually-logged metrics from the tracker (
~~spreadsheetor profile path) - Product-telemetry metrics from Honeycomb via the Honeycomb MCP (
~~observability) when wired — same sourcing rules as KPI Breach Watcher - Flag any metric that could not be retrieved; do not invent values
- Manually-logged metrics from the tracker (
-
Drafts the period narrative using the same output shape as
/performance:performance-narrative(Board Narrative Writer):DRAFT FOR HUMAN REVIEW — not board-ready. Verify every figure before distribution. HEADLINE: [bottom line — the one thing that matters most this period] WHY: 1. [supporting point] 2. [supporting point] WHAT'S NEEDED: [decision/investment/awareness-only — be explicit] FULL DETAIL: [metric-by-metric breakdown, all movements, for reference] -
Applies the trust spine from
performance-narrative: source-tag every figure ([sourced: …]or[unverified — …]), surface load-bearing assumptions at the top (after the draft banner), and do not upgrade unverified numbers. This agent does not pass the board-ready gate — it produces a draft only. Recommend/performance:performance-narrativefor final polish after the human has verified inputs.
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 · 54 lines · 44 tokens per session scan A 4ec71098ff81
cadence-reporter is an agent published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 715 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-09-03.
Other agents, from other repositories
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
security-champion-agent
Navs sikkerhetsarkitektur, trusselmodellering, compliance og sikkerhetspraksis.
accessibility-agent
WCAG 2.1/2.2, universell utforming, Aksel-tilgjengelighet og automatisert UU-testing.
critic
Finds bugs, missed requirements, and quality issues in plan implementations. Spawned after all tasks pass review for a final sweep.
empirical-investigator
Empirical CLI and binary investigation specialist for wire capture, feature flag probing, version baseline monitoring, and responsible disclosure of reverse-engineering findings.