Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jjanczur/tyran/plugin install tyranWrote 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/jjanczur/tyran/status)<a href="https://agentmods.dev/skills/jjanczur/tyran/status"><img src="https://agentmods.dev/badge/skills/jjanczur/tyran/status.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.00058 | $0.00487 |
| Opus 5 | $0.00029 | $0.00244 |
| Sonnet 5 | $0.00012 | $0.00097 |
| Haiku 4.5 | $0.00006 | $0.00049 |
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 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.
What it actually says
Status
Answer from the journal, never from memory.
J=$(ls -t .tyran/state/*/journal.jsonl 2>/dev/null | head -1)
node "${CLAUDE_PLUGIN_ROOT}/scripts/project.mjs" "$J" --out-dir "$(dirname "$J")"
node "${CLAUDE_PLUGIN_ROOT}/scripts/board.mjs" --dir .tyran
node "${CLAUDE_PLUGIN_ROOT}/scripts/journal.mjs" tail "$J"
node "${CLAUDE_PLUGIN_ROOT}/scripts/journal.mjs" open-spawns "$J"
Then report, in this order and no longer than a screen:
- If
.tyran/state/paused-until.jsonexists, the pause comes FIRST: which window, when it resumes, andnode "${CLAUDE_PLUGIN_ROOT}/scripts/overnight.mjs" statusoutput. Everything below it is context for a session that is deliberately not working. - The progress line:
PROGRESS: NN% · X/Y tickets · phase: <name> · last merge: <sha>. - Agents with no report yet — the ones from
open-spawns. Say how long each has been open. An agent that has been running for an hour is the most useful thing on this screen and the easiest to overlook. - Open gates, and who is waiting on whom.
- Any lease released by someone who did not hold it. The projection surfaces these; they mean two agents believed they owned the same worktree.
- The resume steps from the last checkpoint.
End by pointing the operator at .tyran/state/board.html — the kanban view
of everything above, refreshed on every subagent stop and every merge.
If there is no journal, say exactly that and suggest /tyran:setup. Do not
reconstruct a status from the git log — a plausible status is worse than none,
because it will be believed.
Change nothing. This command reads.
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 First seen · 40 lines · 58 tokens per session scan A c3a22efb3983
status is a skill published in the GitHub repository jjanczur/tyran (86 stars, last pushed 3d ago), licensed Apache-2.0. It adds 58 tokens to every session and 487 once invoked, about $0.0003 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
docs-keeper
Maintains the four living documents of a hi-vibe project: CLAUDE.md (lean project context — constraints, pitfalls, rationale), per-folder MODULE.md (detailed design), handover.md (session-to-session context log), CHANGELOG.md (substantive change history, Keep a Changelog). Use for /hi-vibe:init, :handover, :log…
prototype
Full-stack feature prototyping — requirements to deployment with checkpoint gates.
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
ring:planning-large-features
Planning the 8-gate Large Track pre-dev workflow (research, PRD, feature map, TRD, API contract, data model, dependency map, plan) with per-gate human approval. Use for features 2+ days that add dependencies, data models, multi-service integration, or new architecture. Skip for small features (use…
ceo-delegation
A task-delegation workflow that tells an agent to assign work to sub-agents, monitor their progress, and review their results rather than doing the work itself.