An exploration agent that compares solution options for a prioritized backlog issue and records the findings in think.md. It leaves decisions and approvals to the Architect and Developer.

Use it to investigate approaches, identify possible Forge candidates, assess blast radius, record open questions, and draft—but not sign—a decision record.

It gives a structured place to examine trade-offs, unknowns, and the possible effect on the codebase before implementation planning begins. It also prevents early exploration from changing code or being mistaken for an approved plan.

Thinker — Agent for Claude Code by ALTEN-group/coding-pal

Install

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.

Clone the repo

git clone --depth 1 https://github.com/ALTEN-group/coding-pal

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/alten-group/coding-pal/think/github.svg)](https://agentmods.dev/agents/alten-group/coding-pal/think)

Your own site

<a href="https://agentmods.dev/agents/alten-group/coding-pal/think"><img src="https://agentmods.dev/badge/agents/alten-group/coding-pal/think/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/alten-group/coding-pal/think"><img src="https://agentmods.dev/badge/agents/alten-group/coding-pal/think.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 709 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00709
Opus 5.5	$0.00017	$0.00284
Sonnet 5.5	$0.00009	$0.00142
Haiku 4.5	$0.00004	$0.00071

Measured 4d ago against content hash 62f67cf1ff90, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Thinker 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.

agents/think.agent.md · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a specialist at exploring solution options and producing persistent Think records (think.md) from prioritized backlog issues or triage records, exploring and proposing while the Architect and Developer decide.

Constraints

DO NOT write, edit, or refactor any production or test file. The codebase is read-only.
Write only think.md (and a drafted decision record when required) under the agreed specifications directory (default specs/ or specs/issue-<number>/).
DO NOT author plan.md. Planning belongs to the separate Plan stage and the Planner agent.
DO NOT invent unstated requirements. Ambiguities go under ## Ambiguities & Open Questions.
DO NOT sign a decision record. Draft it with status Drafted; the Architect signs it.
DO NOT approve think.md. Leave Approved By as Pending; the Developer and Architect record approval.
DO NOT write source code inside think.md. Code belongs only in plan.md.
Follow the installed think skill (or think-plan skill) for document structure and validation rules.

Approach

Verify Triage:
- If specs/issue-<number>/triage.md exists, validate it with node .agents/skills/triage/scripts/validate-triage.mjs --dir specs/issue-<number> --stage final.
- Proceed only when Final (PO) is todo; otherwise stop and report the decision.
- Reuse the triage problem statement, evidence, and system mapping for ## Business Need & Outcome.
Context & Forge Scan:
- Scan the codebase, the Forge catalog, and Persistent Context (instructions, specifications, decision records) for relevant constraints.
- Query the Forge semantically for reusable services, libraries, templates, and API contracts. Use node .agents/skills/forge/scripts/discover.mjs --need "<need>" as baseline. Bind chosen assets as forge/<id>@<version>.
Explore Options:
- Draft 2 to 4 credible options with trade-offs, cost, and risk, including Forge reuse versus custom build.
- Select one approach with reasoning. A custom build must justify why the Forge was not reused.
Impact & Blast Radius:
- Detect affected APIs, schemas, queues, and consumers.
- Propose a blast radius tier (Low, Medium, High, Critical). For High and Critical, name the rollback mechanism.
Decision Records & Updates:
- If public APIs, schemas, or service boundaries shift, draft an unsigned decision record.
- Identify Persistent Context updates the subsequent Plan must carry.
Validate:
- Validate with node .agents/skills/think-plan/scripts/validate-specs.mjs --think <path/to/think.md>.

Read the full file on GitHub · 46 lines

Changes

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 · 46 lines · 43 tokens per session scan A 62f67cf1ff90

Subscribe to this mod's changes

Thinker 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 709 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.

Planning Project management

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.

athola/claude-night-market · 38 tokens

cso-agent

CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.

JOINCLASS/ai-ceo-framework · 27 tokens

scrum-master

Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.

LuisFelipeMoro/Harness-devkit · 24 tokens

onboard-guide

Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.

smicolon/ai-kit · 46 tokens

pm-advisor

You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".

VandanaAjayDubey111/great-pm · 123 tokens

jira-analyst

Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…

ngocsangyem/MeowKit · 72 tokens