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/boshu2/agentops/statusnpx skills add boshu2/agentops --skill statusgit clone --depth 1 https://github.com/boshu2/agentopsWhat 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.00023 | $0.00712 |
| Opus 5 | $0.00012 | $0.00356 |
| Sonnet 5 | $0.00005 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
status 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
Status
A status snapshot is trustworthy exactly when every line traces to an artifact that exists on disk right now; the first inferred line turns the report into a guess wearing a report's clothes.
Report only observable local facts: available intent and verdict artifacts and
their counts; deterministic check results; evidence recency; and unavailable or
corrupt sources. The canonical durable stores are .agents/ao/intents/sha256
and .agents/ao/verdicts/sha256. Subject manifests are caller-supplied: report
them only when the caller names their location, otherwise disclose them as
not_checked. When .agents/ao evidence exists, report which stored artifact
kind is newest and label that conclusion as evidence recency, not runtime phase
or process activity. The ao status snapshot emits the two counts plus that
newest-artifact recency conclusion, not a per-artifact digest or timestamp
listing; report a specific artifact's digest or timestamp only when the caller
asks about a named artifact.
Always disclose checked and not_checked. Runtime phase, execution elapsed
time, tool-call activity, and remaining work are not_checked unless a caller
provides a separate authoritative source for them.
ao status is the evidence-store view. It validates content-addressed artifact
names and content before counting them, reports corrupt and unavailable entries,
and shows only intent/verdict counts plus evidence recency. Retired legacy
surfaces (session indexes, provenance summaries, knowledge-health signals) are
not aggregated into this command.
Distinct state classes stay distinct in every status report: tracker state belongs to the tracker, Git state to Git, factory or runtime state to the selected factory's own doors, deterministic-check results to the executable that produced them, and semantic validation to a fresh verdict. Report each from its own authority, never merged into one blended "health" claim — factory-complete, checks-green, and AgentOps-PASS are three different facts.
Status does not inspect work queues, assign priority, claim work, infer a next action, repair records, govern retries, or change any state. Optional Git or tracker metadata may be displayed only when the caller supplies it; absence cannot change the report interpretation.
Named failure mode — recency-as-activity: reading "newest artifact is a verdict" as "validation is running", which invents a runtime phase from a timestamp.
Anti-pattern: filling not_checked gaps with plausible narrative so the
snapshot feels complete. Corrective: report the gap as a gap; an honest hole
outranks a smooth story.
Return the snapshot and stop.
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 · 75 lines · 23 tokens per session scan A 4f063f2ae148
status is a skill published in the GitHub repository boshu2/agentops (431 stars, last pushed 4d ago), licensed Apache-2.0. It adds 23 tokens to every session and 712 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 skills, from other repositories
brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning, not for a decisive verdict on whether to adopt or switch to a specific external technology, library, or…
doc-review
Use when the user asks to review or critique a prose planning document — a plan, spec, PRD, requirements doc, or design doc.
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
autolearn
Compound a solved problem into a durable in-repo learning doc. Use when a verified non-trivial fix lands, the user says "compound this", "document this fix", or "remember this". This is the automatic-capture entry point; for an explicitly requested one-off write-up, use compound.
commit-push-pr
Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
doubt-driven
Doubt-driven adversarial review. Use when correctness matters more than speed, the code is unfamiliar, stakes are high, a claim can't be checked by the type system or compiler, or verifying now is cheaper than debugging later.