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/aneja5/forge-skills/observegit clone --depth 1 https://github.com/aneja5/forge-skillsWrote 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/aneja5/forge-skills/observe)<a href="https://agentmods.dev/commands/aneja5/forge-skills/observe"><img src="https://agentmods.dev/badge/commands/aneja5/forge-skills/observe.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.1 | $0.00021 | $0.00152 |
| Opus 5 | $0.00010 | $0.00076 |
| Sonnet 5 | $0.00004 | $0.00030 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
observe 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 5d 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
Invoke the forge-skills:observability skill.
Define correlation ID flow through every service boundary. List golden signals per service — Rate, Errors, Duration (p50/p95/p99), Saturation. Define SLOs per user-facing endpoint with page-worthy vs ticket-worthy alert thresholds. Every alert links to a runbook. Establish log levels, structured JSON schema, retention. Configure trace sampling (head-based baseline + tail-based for errors). Document PII redaction rules (cross-ref security-and-compliance).
After writing: "Observability written to .forge/observability.md. Pair with /incident for runbooks."
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.
- 5d ago First seen · 15 lines · 21 tokens per session scan A 92ca977fc0b8
observe is a command published in the GitHub repository aneja5/forge-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 152 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-31.
Other commands, from other repositories
feature
Implement a ready-for-agent feature ticket in this checkout. Do not expand the ask.
bug
Reproduce then TDD-fix a ready-for-agent bug ticket in this checkout. Web bugs get a browser repro first.
ci
Watch gh pr checks until green and fix failures on this branch. Do not merge.
docs
Docs-only change for a ready-for-agent ticket. No application code.
lead
Tech lead: classify, quiz, ticket on the owning repo, dispatch. Do not implement.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.