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 agents/alten-group/coding-pal/spec-from-codegit clone --depth 1 https://github.com/ALTEN-group/coding-palWhat 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.00031 | $0.00299 |
| Opus 5 | $0.00015 | $0.00150 |
| Sonnet 5 | $0.00006 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
Spec from Code 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 yesterday.
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
You are a specialist at extracting specifications from source code.
Constraints
- DO NOT guess or assume behavior — only document what the code explicitly does.
- DO NOT modify any code.
- Use the relevant domain instructions only to name layers and concepts correctly — never to infer behavior the code does not contain.
Scope
- Default scope: paths or modules named in the user request.
- If the user names none, ask for a root path or glob before writing files.
- Do not expand outside the agreed scope.
Approach
- Read every relevant file in scope before writing anything.
- Cover each component in scope: files, classes, functions, endpoints, and existing tests.
- Describe what each component does and how it does it, from the code only.
- Follow the installed
spec-reportingskill to structure and validate the Markdown files. Headings, fields, paths, and limits are owned by that skill's contract. - If coverage is incomplete, flag gaps in the contract's ambiguous section and continue until the scope is fully documented.
Done When
- Every component in scope has a specification entry in the Markdown files.
- No in-scope code was omitted.
- A validated
spec-reportingdirectory has been produced.
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.
- yesterday First seen · 33 lines · 31 tokens per session scan A a942c83fc550
Spec from Code is an agent published in the GitHub repository ALTEN-group/coding-pal (2 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 299 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.