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/mikeprasad/aria-knowledge/stitchnpx skills add mikeprasad/aria-knowledge --skill stitchgit clone --depth 1 https://github.com/mikeprasad/aria-knowledgeWrote 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/mikeprasad/aria-knowledge/stitch)<a href="https://agentmods.dev/skills/mikeprasad/aria-knowledge/stitch"><img src="https://agentmods.dev/badge/skills/mikeprasad/aria-knowledge/stitch.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.00055 | $0.02624 |
| Opus 5 | $0.00028 | $0.01312 |
| Sonnet 5 | $0.00011 | $0.00525 |
| Haiku 4.5 | $0.00006 | $0.00262 |
Grade A, and why
stitch 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 4d 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 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.
- 4d ago First seen · 142 lines · 55 tokens per session scan A ef417a1ee17e
stitch is a skill published in the GitHub repository mikeprasad/aria-knowledge (16 stars, last pushed 8d ago), with no licence file. It adds 55 tokens to every session and 2,624 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
flow
Personal task and agent-session manager. CLI binary is flow (assumed on PATH) and stores metadata in /.flow/flow.db (SQLite). Use this skill when the user asks about their work, tasks, or projects in any natural phrasing — including but not limited to: "what's left", "what's remaining", "what's pending", "what do I…
gherkin-ticket
Shape every ticket around a scannable use-case before it's filed. ALWAYS use when the user says 'file a ticket', 'create a ticket', 'file tickets for', 'open an issue', 'add a ticket', 'log a bug', or whenever drafting, titling, or rewriting a ticket. Turns vague, implementation-first tickets into an outcome title (…
god
Cross-project omniscient status view — like top for Catalyst work streams. ALWAYS use when the user says '/god', 'what's happening across projects', 'what's running', 'show me all active work', 'what orchestrators are active', 'what sessions are running', or asks a free-form question about cross-project Catalyst state…
ticket-compound
Compound-engineering capture + curation for a finished ticket — the engineering feedback loop. Harvests the Friction sections that phase agents left in their artifacts plus the git diff, writes a structured entry to the shared learnings store (thoughts/shared/learnings/), prunes/amends stale notes there autonomously…
ticket-retro
Cross-ticket retrospective VIEW (CTL-789 Loop C / CTL-814). ALWAYS use when a ticket's PR has merged and merge-pr's post-merge deploy-verification (CTL-2232) has resolved a terminal sentinel for it (the workflow's compound closing step — relay-native trigger, CTL-2244; see ../compound-estimate/references/trigger.md)…
groom-backlog
Groom Linear backlog to identify orphaned issues, incorrect project assignments, and health issues.