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 telus-labs/stagecraft --skill implementgit clone --depth 1 https://github.com/telus-labs/stagecraftWrote 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/telus-labs/stagecraft/implement)<a href="https://agentmods.dev/skills/telus-labs/stagecraft/implement"><img src="https://agentmods.dev/badge/skills/telus-labs/stagecraft/implement/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/telus-labs/stagecraft/implement"><img src="https://agentmods.dev/badge/skills/telus-labs/stagecraft/implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00122 | $0.01603 |
| Opus 5.5 | $0.00049 | $0.00641 |
| Sonnet 5.5 | $0.00024 | $0.00321 |
| Haiku 4.5 | $0.00012 | $0.00160 |
Grade A, and why
implement 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 1mo 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement a Change
A four-step workflow for implementing improvements: plan, execute, verify, commit. Use this for focused changes (a few files, clear scope) where the full /pipeline would be overkill.
When to use this vs. /pipeline: if the change needs requirements refinement (PM), architectural decisions (Principal), or touches multiple areas (backend + frontend + infra), use /pipeline instead.
Before Starting
Load context about the project and the change:
- Read
docs/audit/00-project-context.mdif it exists — lint command, test command, framework, conventions. - Read
docs/audit/01-architecture.mdif it exists — component map and dependency graph. - Read
docs/audit/10-roadmap.mdif it exists — the sequenced improvement plan. - Read
pipeline/context.mdif it exists — open questions, prior decisions, fix log. - If the project has a AGENTS.md, read the coding standards sections.
- If none of these exist, ask the user: "What are this project's lint/test commands, and are there coding conventions I should follow?"
Identify what to implement. The user may:
- Name a specific item from the roadmap — look it up in
docs/audit/10-roadmap.md - Describe the change directly — use their description as the spec
- Say "next item" — pick the next unfinished item from the roadmap, respecting the sequence
If the scope is unclear, ask before planning.
Step 1: Plan
Write a detailed implementation plan before touching any code. The goal is to surface problems, missing context, and open questions before investing effort in coding.
The plan covers:
-
Context — What's wrong today and the concrete impact. Why fix it now rather than later.
-
Approach — The strategy. If there are multiple ways to do this, briefly note the alternatives and why this approach wins. Keep it to 2-3 sentences.
-
File-by-file changes — Every file that needs modification, with the specific change described precisely enough for someone to review the plan without reading the code.
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.
- 1mo ago First seen · 124 lines · 122 tokens per session scan A a76bad6486b2
implement is a skill published in the GitHub repository telus-labs/stagecraft (6 stars, last pushed 19d ago), licensed MIT. It adds 122 tokens to every session and 1,603 once invoked, about $0.0005 per session on Opus 5.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 skills, from other repositories
semantix-guide
Troubleshoot and configure Semantix capabilities: Skills (project/custom/global/builtin priority, discovery dirs), Commands (override order, /dir:file naming), Hooks (11 events, automatic project loading, matchers, timeouts), MCP (semantix-agent.toml + .mcp.json + plugin packages, autostart), plugin packages…
semantix
Install and use the semantix memory kernel as a middleware in your agent: extract user preferences / workflows / experience from past sessions, retrieve and inject them on demand. One binary + your agent's own tools.
intuitive-shape
Shape unsettled product ideas into bounded bets before planning; excludes settled fixes and approved execution.
intuitive-doc
Maintain README.md, ARCHITECTURE.md, STATUS.md, and docs/human/ when they drift or need cleanup.
intuitive-reduce-entropy
Find and rank material simplification candidates when the cleanup target or plan risks are unclear.
research
Investigate a bounded question using multiple sources or a cited report; answer single facts and codebase questions directly.