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 skills/sethgammon/citadel/telemetrynpx skills add SethGammon/Citadel --skill telemetrygit clone --depth 1 https://github.com/SethGammon/CitadelWhat 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.00068 | $0.02994 |
| Opus 5 | $0.00034 | $0.01497 |
| Sonnet 5 | $0.00014 | $0.00599 |
| Haiku 4.5 | $0.00007 | $0.00299 |
Grade A, and why
telemetry 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 3d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/telemetry — Telemetry Hub
When to Use
- "What does Citadel track?" / "What telemetry does it have?"
- "What did this session cost?" / "How much have I spent?"
- "How do I turn off the cost alerts?" / "Can I disable telemetry?"
- "Show me hook activity" / "What hooks fired?"
- "What trust level am I at?"
- Directly:
/telemetry
Routed here by /do for: "telemetry", "what did this cost", "session stats",
"session cost", "how much did that cost", "what hooks fired", "trust level",
"show me telemetry", "cost breakdown", "spending".
Commands
| Command | Behavior |
|---|---|
/telemetry |
Full hub — stats + command directory + settings |
/telemetry --costs |
Cost section only: session, today, all-time, by campaign |
/telemetry --hooks |
Hook activity only: last 20 fires with timing and outcomes |
/telemetry --verify |
Telemetry and artifact integrity check: verify hashes/signatures, flag tampered records, report legacy records |
/telemetry --config |
Show current telemetry settings from harness.json |
/telemetry off |
Disable session summary, reduce hook verbosity |
/telemetry on |
Re-enable all telemetry |
/telemetry --threshold N |
Set cost alert threshold step (e.g. --threshold 10 = alert every $10) |
Protocol
Step 1: COLLECT DATA
Read the following in parallel. All are optional — treat missing files as zero/empty.
Live session cost:
- Run
node scripts/session-tokens.js --today 2>/dev/null— captures real token data - If unavailable, read
.planning/telemetry/cost-tracker-state.jsonfor burn rate - Real cost is always preferred over estimated. Mark clearly:
$X.XXvs$X.XX (est)
Historical costs:
- Run
node scripts/session-tokens.js --all 2>/dev/nullfor all-time real totals - Read last 20 lines of
.planning/telemetry/session-costs.jsonlfor recent sessions - For each entry: prefer
real_cost>override_cost>estimated_cost
Hook activity:
- Read last 20 lines of
.planning/telemetry/hook-timing.jsonl - For each
event: "timing"entry: extracthook,duration_ms,timestamp - For each
event: "counter"entry: extracthook,metric - Check
.planning/telemetry/hook-errors.jsonl(last 20 lines) for recent blocks
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.
- 3d ago First seen · 275 lines · 68 tokens per session scan A c582bfb29d0d
telemetry is a skill published in the GitHub repository SethGammon/Citadel (914 stars, last pushed 6d ago), licensed MIT. It adds 68 tokens to every session and 2,994 once invoked, about $0.0003 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 skills, from other repositories
debrief
This skill should be used when the user asks to "debrief", "record what happened", "session summary", "write a debrief", or wants to capture session activity (commits, task state changes, decisions, issues) into a structured record for the next session.
refit
This skill should be used when the user asks to "refit a workflow", "upgrade a workflow", "update workflow scaffolding", or wants to bring an existing workflow's scaffolding files up to date with the current Spacedock version.
fo-dispatch-recovery
Claude dispatch failure recovery — Break-Glass Manual Dispatch (the manual Agent() template) and Context Budget Failure/Dead Ensign Handling (the budget-unavailable stderr conditions, the recovery clause, dead-ensign bookkeeping). Read ONLY at its resident triggers inside claude-fo-dispatch.md — a non-zero or…
fo-status-viewer
First-officer status query/mutate/display surface — the status command flag docs, --set field docs, canonical captain-facing invocations, the Captain-Facing State Display rendering, and the GitHub-issue-filing approval gate. Invoke at the first ad-hoc status question, --set mutation, --next-id/--resolve lookup, or…
present-gate
First-officer gate-presentation rendering — the captain-facing gate-review template and assembly rules, including workflow-owned finding labels. Invoke at the gate point after the FO has decided a stage must be presented.
agent-workflow-playbook
AI Agent Workflow & Skill Architecture Guide — turn expert work into measurable, reusable agent systems. Covers workflow discovery, skill decomposition, harness design, evaluation, human escalation, observability, cost control, and multi-agent orchestration. Includes a measured marketing-delivery case: 15 people × 3–4…