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/retro)<a href="https://agentmods.dev/skills/jjanczur/tyran/retro"><img src="https://agentmods.dev/badge/skills/jjanczur/tyran/retro.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.00062 | $0.02105 |
| Opus 5 | $0.00031 | $0.01052 |
| Sonnet 5 | $0.00012 | $0.00421 |
| Haiku 4.5 | $0.00006 | $0.00211 |
Grade A, and why
retro 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 8d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retro
The only loop through which Tyran gets better at this repo instead of repeating the same mistake every initiative.
You normally do not have to invoke this. The Stop gate refuses one turn
when an initiative has all its tickets merged and no retrospective recorded
since the last merge. This skill is what you run when it does — or when you
want one early.
1. Spawn the retrospector
Spawn tyran:retro at the tier node "${CLAUDE_PLUGIN_ROOT}/scripts/tiers.mjs" --role retro resolves, over the initiative's PLAN.md, NOTES.md, the
agents' reports, and the initiative's git log.
Do not do this work yourself in the conducting session. The retrospector's value comes from reading the record cold; a conductor reviewing its own initiative rates its own decisions, and rates them well.
2. Record the outcome — including "nothing"
Every retro ends with a journal entry, whatever it concluded:
node "${CLAUDE_PLUGIN_ROOT}/scripts/journal.mjs" append "$J" retro.entry "$INIT" \
--actor retro --data '{"kind":"skill","target":"skills/run/SKILL.md","confidence":"medium"}'
kind is skill, agent, script, doc, knowledge — or skipped
with the reason, when the judgement is that this initiative has nothing worth
changing. That is a correct outcome and it settles the gate exactly like any
other. A retro that always finds something is not learning, it is padding.
When kind is skill, follow skill-writing. New skills are AUTO class —
you may commit one without asking — and that is only safe against a standard.
It carries the admission test (a skill nothing already points at is a library
entry), the description budget you are spending on every future session, and
the activation test that proves the thing fires at all. A skill that never
triggers costs its description on every turn and returns nothing.
3. Write down what is true about THIS repo
Durable facts go to .tyran/knowledge/<topic>.yaml, which is AUTO class —
the retrospector may write it without asking:
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.
- 8d ago First seen · 183 lines · 62 tokens per session scan A e0547c17e1bd
retro is a skill published in the GitHub repository jjanczur/tyran (86 stars, last pushed 5d ago), licensed Apache-2.0. It adds 62 tokens to every session and 2,105 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.