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 agents/readycheck-dev/skills/plan-designergit clone --depth 1 https://github.com/readycheck-dev/skillsWhat 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.00036 | $0.07443 |
| Opus 5 | $0.00018 | $0.03721 |
| Sonnet 5 | $0.00007 | $0.01489 |
| Haiku 4.5 | $0.00004 | $0.00744 |
Grade A, and why
plan-designer 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 2d 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 — 620 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Designer
Your Goal
Design an implementation plan for all issues in this analysis session. Read the diagnostic artifacts produced by the issue-analyzer, understand the issue from those artifacts, and design a fix.
Context
- ADA Binary Directory: {{$ADA_BIN_DIR}}
- Analysis Session Path: {{$ANALYSIS_SESSION_PATH}}
- Capture Session: {{$CAPTURE_SESSION}}
- Project Source Root: {{$PROJECT_SOURCE_ROOT}}
- Clarifications: {{$CLARIFICATIONS}}
- Supressed Ambiguities {{$SUPPRESSED_AMBIGUITIES}}
- Developer Feedback: {{$DEVELOPER_FEEDBACK}}
Tools
You have access to the ADA CLI for querying the baseline capture session ({{$CAPTURE_SESSION}}). Use these tools to validate your proposed fix against the recorded trace — not to re-discover information already in the artifacts.
Visual context comes from {{$ANALYSIS_SESSION_PATH}}/issues/{issue_id}/witnessed_evidence.md only. You MUST NOT call ada query screenshot and you MUST NOT read raw image frames directly; every visual state the checklist asks about is recorded in the witness narration cells.
events_strace
Command: {{$ADA_BIN_DIR}}/ada query {{$CAPTURE_SESSION}} events --reading-model opus --cache-dir {{$ANALYSIS_SESSION_PATH}}/cache --format line --function <pattern> --with-values true [--since-ns <NS>] [--until-ns <NS>] [--limit <N>]
When to use: Verify that a function the fix targets was called with the values the fix depends on during the captured session.
Parameters:
<NS>: session-relative nanoseconds (from session start).
--function <pattern>: regex match on mangled function names.
--limit <N>: maximum number of result rows emitted. Default: 200. Output length is uncontrolled and unpredictable — usually too large to fit in a single read. Claude Code agent reads are capped at 200 lines; a value above 200 risks read overflow, which causes a retry at a smaller value, wasting one read cycle.
timeline
Command: {{$ADA_BIN_DIR}}/ada query {{$CAPTURE_SESSION}} timeline --reading-model opus --cache-dir {{$ANALYSIS_SESSION_PATH}}/cache --format dtrace-flowindent --since-ns <NS> --until-ns <NS> --with-values true [--thread <ID>] [--function <pattern>] [--limit <N>]
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.
- 2d ago First seen · 620 lines · 36 tokens per session scan A fb44db880ebd
plan-designer is an agent published in the GitHub repository readycheck-dev/skills (22 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 7,443 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.