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/tta-lab/ttal-cli/plan-triagenpx skills add tta-lab/ttal-cli --skill plan-triagegit clone --depth 1 https://github.com/tta-lab/ttal-cliWrote 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/tta-lab/ttal-cli/plan-triage)<a href="https://agentmods.dev/skills/tta-lab/ttal-cli/plan-triage"><img src="https://agentmods.dev/badge/skills/tta-lab/ttal-cli/plan-triage.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.00019 | $0.00936 |
| Opus 5 | $0.00010 | $0.00468 |
| Sonnet 5 | $0.00004 | $0.00187 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
plan-triage 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Triage
Triage plan review findings: categorize each issue, fix what's actionable, then report.
You already have the plan and its review issues in context. No need to search or re-read — just categorize, fix, and report.
Usage
/plan-triage
Run this after ttal go <uuid> has identified issues. The plans and issues are already in your conversation context.
Phase 1: Categorize
For each issue from the plan review, categorize it:
Actionable (fix now)
- Gaps that would block a worker
- Wrong assumptions verified against the codebase
- Missing error handling or edge cases that matter
- Under-engineered: shortcuts that will create tech debt
- Ambiguities that can be clarified from the codebase
Format: [FIX] <summary> — <why it matters>
False Positive (push back)
- Assumption that's actually correct (verified)
- Edge case that can't happen in this context
- "Over-engineered" flag on complexity that's genuinely needed
Format: [FALSE POSITIVE] <summary> — <why it's wrong>
Deferrable (follow-up)
- Nice-to-have improvements, not blockers
- Style preferences in the plan structure
- Over-engineered parts that work fine, just aren't minimal
Format: [DEFER] <summary> — <why it can wait>
Needs Neil (can't resolve without human input)
- Business requirements or product decisions
- Priority tradeoffs
- Integration points the reviewer can't verify
Format: [ASK] <summary> — <question for Neil>
Phase 2: Fix
Address all [FIX] items directly in the plan using flicknote:
Update a section
echo "updated content" | flicknote modify --section
Append missing steps
echo "new content" | flicknote append
Insert before/after a section
echo "content" | flicknote insert --after
For each fix:
- Make the change in the flicknote plan
- Keep fixes minimal — address the issue, don't redesign the plan
- If a fix requires significant rewriting, recategorize it as
[ASK]instead
Phase 3: Report
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 · 128 lines · 19 tokens per session scan A 4c91131ffa71
plan-triage is a skill published in the GitHub repository tta-lab/ttal-cli (23 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 936 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…