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/sp-complete-designnpx skills add tta-lab/ttal-cli --skill sp-complete-designgit 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/sp-complete-design)<a href="https://agentmods.dev/skills/tta-lab/ttal-cli/sp-complete-design"><img src="https://agentmods.dev/badge/skills/tta-lab/ttal-cli/sp-complete-design.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.00026 | $0.00387 |
| Opus 5 | $0.00013 | $0.00193 |
| Sonnet 5 | $0.00005 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
sp-complete-design 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 5d 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.
What it actually says
Complete a Design
Finalize an existing FlickNote design or plan without starting review or implementation.
1. Load the Note
Read the full note and its structure:
flicknote detail flicknote detail --tree
The note must live in the orientation project. Move it there if needed.
2. Review as the Implementer
Check:
- Could someone execute it without asking for missing context?
- Are file paths, commands, expected results, and ordering accurate?
- Are goal, anti-goals, exit criteria, tests, risks, and dependencies clear?
- Does any stage still hide a design decision?
- Should an oversized plan be split into deliverable phases?
Write fixes directly back with flicknote modify, replace, append, or section operations.
3. Resolve Missing Context
Search the repository, prior notes, or external sources for facts that do not require user judgment. Fold useful findings into the note.
Ask the user only for decisions that materially change scope, behavior, or trade-offs. Persist the answer in FlickNote before continuing.
4. Final Check
Re-read the updated note from top to bottom. Confirm that:
- The note is the single source of truth
- No required work is stored only in chat
- No Taskwarrior task, annotation, or task tree is required
- No unresolved question blocks execution
5. Hand Back
Return:
- FlickNote ID
- One paragraph describing what and why
- Major stages
- Remaining risks, if any
Keep the summary under 200 words. Stop there. Do not invoke review, ttal go, goal-impl, or any other next phase.
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.
- 5d ago First seen · 56 lines · 26 tokens per session scan A fa2a53211454
sp-complete-design is a skill published in the GitHub repository tta-lab/ttal-cli (23 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 387 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…