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 ALTEN-group/coding-pal --skill think-plangit clone --depth 1 https://github.com/ALTEN-group/coding-palWrote 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/alten-group/coding-pal/think-plan)<a href="https://agentmods.dev/skills/alten-group/coding-pal/think-plan"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/think-plan/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/alten-group/coding-pal/think-plan"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/think-plan.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.00055 | $0.00793 |
| Opus 5.5 | $0.00022 | $0.00317 |
| Sonnet 5.5 | $0.00011 | $0.00159 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
think-plan 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 8d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Think & Plan
Produce deterministic think.md and plan.md specification artifacts that AI build agents can consume without ambiguity, error compounding, or token waste.
When to Use This Skill
- A business need, user story, issue, or RFC must be transformed into an architectural analysis (
think.md) before implementation (Phase 1: Think). - An existing, validated architectural specification (
think.md) must be translated into an atomic, phased implementation checklist (plan.md) with explicit verification commands and bootability checks (Phase 2: Plan). - A GitHub Action or CI workflow triggered on issue creation must autonomously generate or validate specifications before triggering build agents.
Path resolution
Resolve references/ and scripts/ relative to this skill's install directory (the folder that contains this SKILL.md), not the consumer repository root or the current shell cwd. If the skill was installed under .agents/skills/think-plan/ or .claude/skills/think-plan/, use that base path.
Workflow
- Read
references/think-plan-contract.mdnow — it is the authoritative source for document structure, required headings, step schemas, and verification invariants. Scope exploration and architectural choices are owned by the callingThink Planneragent, active planning session, or issue trigger. - Execute the appropriate phase:
- Phase 1 (Think): Analyze business needs and inspect the codebase to author
think.md(capturing business outcome, system request flow, component responsibilities, invariants, and minimal change scope). Validate withnode scripts/validate-specs.mjs --think <path/to/think.md>. - Phase 2 (Plan): Ground strictly in the validated
think.md. Translate its minimal change scope and invariants into an ordered sequence of atomic steps inplan.mdwith explicit files, surgical actions, narrowest verification commands, and bootability checks. Validate withnode scripts/validate-specs.mjs --plan <path/to/plan.md>.
- Phase 1 (Think): Analyze business needs and inspect the codebase to author
- Validate specifications using the deterministic script from this skill's directory:
What ships with it
3 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.
- 8d ago First seen · 49 lines · 55 tokens per session scan A 0cbe3c2407b8
think-plan is a skill published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 6d ago), licensed MIT. It adds 55 tokens to every session and 793 once invoked, about $0.0002 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-09-21.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…