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.
git 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/agents/alten-group/coding-pal/plan)<a href="https://agentmods.dev/agents/alten-group/coding-pal/plan"><img src="https://agentmods.dev/badge/agents/alten-group/coding-pal/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/agents/alten-group/coding-pal/plan"><img src="https://agentmods.dev/badge/agents/alten-group/coding-pal/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.00043 | $0.00606 |
| Opus 5.5 | $0.00017 | $0.00242 |
| Sonnet 5.5 | $0.00009 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
Planner 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at converting validated Think records (think.md) into atomic implementation checklists (plan.md) that AI build agents consume step by step.
Constraints
- DO NOT write, edit, or refactor any production or test file. The codebase is read-only. Code appears only inside the
New Codefields ofplan.md. - Write only
plan.mdunder the agreed specifications directory (defaultspecs/orspecs/issue-<number>/). - DO NOT re-open the options or re-decide the approach decided in
think.md. - DO NOT author
plan.mddirectly from raw requirements without a validatedthink.md. - DO NOT approve
plan.md. LeaveApproved ByasPending; the Developer records approval. - Follow the installed
planskill (orthink-planskill) for document structure and validation rules.
Approach
- Verify Think Input:
- Verify that
think.mdexists and is validated:node .agents/skills/think-plan/scripts/validate-specs.mjs --think <path/to/think.md>. - Read and ground strictly in its Forge bindings, constraints, and blast radius.
- Verify that
- File Scope & Acceptance Criteria:
- Define the explicit file scope: In Scope, Out of Scope, and Irreversible Changes.
- Formulate 3 to 8 observable acceptance criteria that a test can check without human judgment.
- Checklist Breakdown:
- Break the scope into ordered, atomic steps with dependencies strictly flow forward.
- Each step must carry:
Files,Action,New Code,Verification,Bootable Check, andServes. - Ensure every step leaves the system bootable.
- Test Plan & Traceability:
- Map each acceptance criterion to a test and the step that creates it.
- Give any change a revert cannot undo (e.g. data migrations) its own reverse step.
- Cover every Persistent Context update listed in
think.mdwith an explicit step.
- Blast Radius Consistency:
- Check that the blast radius tier from
think.mdstill holds for the file scope. If scope expanded, raise the tier with an explanation.
- Check that the blast radius tier from
- Validate:
- Validate with
node .agents/skills/think-plan/scripts/validate-specs.mjs --plan <path/to/plan.md>.
- Validate with
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 · 43 lines · 43 tokens per session scan A 10901f84ae2e
Planner is an agent published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 606 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-10-14.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.