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/cirwel/unitares/diagnosegit clone --depth 1 https://github.com/cirwel/unitaresWrote 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/cirwel/unitares/diagnose)<a href="https://agentmods.dev/commands/cirwel/unitares/diagnose"><img src="https://agentmods.dev/badge/commands/cirwel/unitares/diagnose.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 | $0.00011 | $0.00540 |
| Opus 5 | $0.00005 | $0.00270 |
| Sonnet 5 | $0.00002 | $0.00108 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
diagnose 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
Start by checking the local workspace cache inventory.
Use the shared helper in this repo:
scripts/client/session_cache.py list
If the newest entry contains parent_agent_id, treat it as lineage context, not
proof that this process should declare the same parent.
Do not verify by bare UUID resume. If you need to test ownership of a cached UUID, use an advanced proof-owned rebind only when a matching current in-process token is available. Do not use legacy cache files as token sources.
If no proof-owned UUID rebind is available, call identity() to inspect current
binding. Use /governance-start to create a fresh process identity. Add
parent_agent_id only for a real handoff from a finished predecessor.
Call identity() first when continuity or binding is unclear.
Then call get_governance_metrics for the current agent using the same continuity data.
Call health_check() only when system health, not agent state, may be part of the issue.
Display:
- whether identity was proof-resumed, freshly created, or created with lineage
- whether lineage was declared through
parent_agent_id identity_statusbound_identitysession_resolution_sourcecontinuity_token_supportedidentity_assurance- deprecation warnings
- whether continuity looks strong or weak
- E, I, S, V
- coherence
- risk score
- verdict
- summary or mode/basin if available
- behavioral vs ODE authority when it is obvious in the response
If health_check() is used, also show:
- overall system status
- degraded checks
- first operator action
Call list_process_bindings() (optionally with agent_uuid=<uuid>) to show live execution-context bindings for the agent. When concurrent_binding_detected is true, surface the bindings[] tuples — each row is {host_id, pid, pid_start_time, transport, tty, last_seen} — so the operator can see which contexts are siphoning the same UUID. See issue #123.
If the live identity differs from the cache inventory, refresh the local slotted cache with the latest uuid, identity fields, and schema_version: 2 using scripts/client/session_cache.py set session --slot <client_session_id-or-codex-session-id> --merge --stamp. Do not write continuity_token to the cache.
Do not dump raw JSON unless the user explicitly asks for it. Prefer a short interpreted summary.
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 · 58 lines · 11 tokens per session scan A 0d33f363e4ce
diagnose is a command published in the GitHub repository cirwel/unitares (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 540 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
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
coder-eval-implement-plan
Implement an approved codereval plan phase by phase with risk-scaled per-phase review, then a final code review.
build
Bulk-build ArcKit artefacts in parallel via subagent-orchestrated waves with resumable state.
test
Run tests with intelligent package filtering and reporting.
nyann:diff-profile
Compare two nyann profiles side-by-side and show what changes between them: hooks, branching, CI, documentation, extras, governance. Useful before switching profiles to understand the impact.
nyann:undo
Safely undo the last commit (or last N commits) on a feature branch. Always previews first. Refuses main/master/develop, merge commits, and pushed commits (override with --allow-pushed).