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 coalesce-labs/catalyst --skill stewardgit clone --depth 1 https://github.com/coalesce-labs/catalystWrote 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/coalesce-labs/catalyst/steward)<a href="https://agentmods.dev/skills/coalesce-labs/catalyst/steward"><img src="https://agentmods.dev/badge/skills/coalesce-labs/catalyst/steward.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.00072 | $0.01363 |
| Opus 5 | $0.00036 | $0.00681 |
| Sonnet 5 | $0.00014 | $0.00273 |
| Haiku 4.5 | $0.00007 | $0.00136 |
Grade A, and why
steward 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/classify-and-estimate.md 2.8 KB
- references/cloud-detection.md 3.7 KB
- references/dispatch.md 4.3 KB
- references/escalation.md 4.0 KB
- references/initiative-setup.md 2.8 KB
- references/readiness.md 2.5 KB
- references/resume.md 3.7 KB
- references/stalls.md 4.2 KB
- references/status-doc.md 2.4 KB
- references/threads.md 2.8 KB
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 · 79 lines · 72 tokens per session scan A d963b863debb
steward is a skill published in the GitHub repository coalesce-labs/catalyst (20 stars, last pushed yesterday), with no licence file. It adds 72 tokens to every session and 1,363 once invoked, about $0.0004 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
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
orchestrator-lanes
A file-based project-management playbook for a specific Claude Code development orchestrator. It organizes work into lanes, plans, dependency steps, validation phases, and shipping stages.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…
lane-contract
A file-based task contract system for describing coding tasks in YAML, including which files a task owns and how it must be checked.
plan-pipeline
Orchestrates the complete planning pipeline: product direction (ceo-review) -> architecture (eng-review) -> implementation plan (start) -> validation (validate) -> execution (execute). Run stages individually or let the orchestrator coordinate the full flow.