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/theam/facility/add-telemetrygit clone --depth 1 https://github.com/theam/facilityWhat 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.00014 | $0.00278 |
| Opus 5 | $0.00007 | $0.00139 |
| Sonnet 5 | $0.00003 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
add-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 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.
What it actually says
Instrument a feature following STANDARD.md's Analytics section.
- Write the event plan BEFORE touching code, in the task notes or PR summary: user story (who acts, what success/failure means), surface (entry points, primary actions, failure/empty/completion states), and the event catalog — started/completed/failed, validation errors, permission denials, cancellations, retries, background-job lifecycle.
- Add event names to this repo's event catalog file — find it (grep for existing event-name constants) and follow its convention. Never hard-code event-name strings at call sites.
- Privacy check on every property: IDs, enums, counts, durations, booleans, route paths, and field names only. No message text, no user content, no names, no credentials, no full URLs. If a property could identify a person or quote their content, it doesn't ship.
- Add or update telemetry tests when event names, sanitization, or required properties change.
- Verify with the repo's telemetry tests, and finish by listing the events added and the failure paths they cover — uninstrumented failure paths are the gap reviewers will catch.
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 · 24 lines · 14 tokens per session scan A 9a725c548440
add-telemetry is a command published in the GitHub repository theam/facility (43 stars, last pushed 4d ago), licensed Apache-2.0. It adds 14 tokens to every session and 278 once invoked, about $0.0001 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.