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 zstevovich/claude-apd --skill apd-mirogit clone --depth 1 https://github.com/zstevovich/claude-apdWrote 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/zstevovich/claude-apd/apd-miro)<a href="https://agentmods.dev/skills/zstevovich/claude-apd/apd-miro"><img src="https://agentmods.dev/badge/skills/zstevovich/claude-apd/apd-miro/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/zstevovich/claude-apd/apd-miro"><img src="https://agentmods.dev/badge/skills/zstevovich/claude-apd/apd-miro.svg" alt="Reviewed on agentmods" width="80" 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.00092 | $0.01629 |
| Opus 5 | $0.00046 | $0.00814 |
| Sonnet 5 | $0.00018 | $0.00326 |
| Haiku 4.5 | $0.00009 | $0.00163 |
Grade A, and why
apd-miro 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 10d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Miro Pipeline Dashboard (Codex)
Creates or updates a pipeline dashboard on the Miro board with:
- Current pipeline status (which step is active)
- Recently completed tasks with durations
- Pipeline metrics (averages, skip rate)
When to use / When to skip
Use when:
- The project has
MIRO_BOARD_URLconfigured inAGENTS.md - A pipeline cycle just completed — update the board with the new result
- The user asked: "update Miro dashboard"
- Start of a session — display current pipeline state on the board
Skip when:
- No Miro board is configured for the project (no
MIRO_BOARD_URL) - The Miro MCP server is not connected or authenticated
- The pipeline hasn't moved since the last update — the board would show the same state
Prerequisite
- Miro MCP server registered in
.codex/config.toml(HTTP transport:https://mcp.miro.com) - MCP authentication completed (Codex prompts on first call)
MIRO_BOARD_URLdefined inAGENTS.md
Procedure
1. Gather data
Pull pipeline state and historical metrics through MCP tools:
apd:apd_pipeline_state() # current step + step timings
apd:apd_pipeline_metrics() # historical runs (timestamp, phase ts, status, adversarial T/A/D, agent counts)
Compute averages and skip rate from the runs list returned by apd:apd_pipeline_metrics(). Pass limit=N to cap the most recent N runs (0 = all, max 200).
2. Create dashboard table on the board
Use Miro MCP create_table to create the dashboard:
Table 1: Pipeline Status
| Step | Status | Time |
|---|---|---|
| Spec | ✅ / ⏳ / — | timestamp |
| Builder | ✅ / ⏳ / — | timestamp |
| Reviewer | ✅ / ⏳ / — | timestamp |
| Verifier | ✅ / ⏳ / — | timestamp |
- ✅ = completed (green sticky note)
- ⏳ = in progress (yellow sticky note)
- — = not started (gray sticky note)
3. Create metrics section
Use Miro MCP create_document for a markdown document:
# APD Pipeline Metrics
**Total tasks:** {count}
**Average duration:** {time}
**Fastest task:** {time}
**Slowest task:** {time}
**Skip rate:** {percentage}
## Average per step
- spec→builder: {time}
- builder→reviewer: {time}
- reviewer→verifier: {time}
What ships with it
4 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.
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.
- 10d ago First seen · 179 lines · 92 tokens per session scan A 6d93a886fc7e
apd-miro is a skill published in the GitHub repository zstevovich/claude-apd (5 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 1,629 once invoked, about $0.0005 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.