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 skills add hams-ollo/zen-agent-skills --skill agent-observatorygit clone --depth 1 https://github.com/hams-ollo/zen-agent-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/skills/hams-ollo/zen-agent-skills/agent-observatory)<a href="https://agentmods.dev/skills/hams-ollo/zen-agent-skills/agent-observatory"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/agent-observatory/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/skills/hams-ollo/zen-agent-skills/agent-observatory"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/agent-observatory.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.00132 | $0.01808 |
| Opus 5.5 | $0.00053 | $0.00723 |
| Sonnet 5.5 | $0.00026 | $0.00362 |
| Haiku 4.5 | $0.00013 | $0.00181 |
Grade A, and why
agent-observatory 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 7d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-observatory
Answer questions that span sessions, and act on a session only where the harness actually lets you. This is the companion to the local reporting surface: the page reports and offers nothing to do, and this skill is where a session-directed action lives when one is available at all.
This skill is a draft. It ships with no profile and reaches no adopter until it has been used
on real work and blessed, per the contribution bar in the target repository's AGENTS.md.
When to use
- A question spans more than one session: what is running, what a wave cost, which skills were used, what failed and how often.
- You want to find a session by what it did rather than by scrolling a list.
- You want to rename a session whose title has gone stale, or hand a message to another session.
When not to use
- You want to start, resume, interrupt, or end a session. This skill does none of those and will not find a way to. Ask the person to run the command themselves.
- You want the numbers rendered rather than answered in prose. Point them at the local page.
- The question is about one session you are already in. Just answer it.
Inputs
Required: nothing. The skill reads what it can reach and says what it could not.
Optional:
- A project scope, to restrict every figure to one project.
- A session id or a description of one, when the question is about a particular session.
Procedure
1. Establish what you can reach, before answering anything
Two sources, and they answer different questions. Check both and say which one an answer came from, because a reader who cannot tell will assume the stronger one.
| Source | Answers | Reach |
|---|---|---|
The observatory store, built by the ingester in the target repository's scripts/observatory/ |
history: skills, tokens, waves, health, per-project figures | every session whose transcript is on this machine |
| The harness's own session management, when exposed | now: what exists, what is running, what is archived, and the actions below | local, remote, and cloud sessions alike |
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.
- 7d ago Changed · +7 lines · -62 tokens per session 503a33982110
- 1mo ago Changed · +7 lines 0ef6afdffd70
- 2mo ago First seen · 136 lines · 194 tokens per session scan A 87a3cd843a33
agent-observatory is a skill published in the GitHub repository hams-ollo/zen-agent-skills (2 stars, last pushed 7d ago), licensed MIT. It adds 132 tokens to every session and 1,808 once invoked, about $0.0005 per session on Opus 5.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 skills, from other repositories
review
Use when explicitly invoked to review a branch diff (or any diff or files pointed at) with a find-only subagent covering rubric and conventions, change conformance against the AC-N and their runtime-verification evidence, and documentation consistency — one plain-text verdict that reaches lgtm only when no dimension…
implement
Use when explicitly invoked to execute a change's tasks.md from the first unticked step: implement each task, run its validation, commit, then run the quality gate and verify every acceptance criterion by observed behavior. Needs no conversation context — the change folder is the whole input. Trigger on…
archive
Use when explicitly invoked to close out a change whose branch has already merged: confirm the merge from git alone, then move the change folder under changes/archive/ with its ship date. Trigger on '/sw:archive', '$sw:archive', 'archive this change', or a request to close out a merged change.
ship
Use when explicitly invoked to run the whole change ladder without stopping — ticket, plan, implementation, quality gate, runtime verification, review to lgtm — deciding every open question autonomously and recording each decision in proposal.md. Trigger on '/sw:ship', '$sw:ship', or a request to take something from…
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…