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/alten-group/coding-pal/spec-reportingnpx skills add ALTEN-group/coding-pal --skill spec-reportinggit 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.00064 | $0.00346 |
| Opus 5 | $0.00032 | $0.00173 |
| Sonnet 5 | $0.00013 | $0.00069 |
| Haiku 4.5 | $0.00006 | $0.00035 |
Grade A, and why
spec-reporting 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 2d 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
Spec Reporting
Produce specification Markdown that a script can validate.
When to Use This Skill
- An agent must extract specifications from source into files.
- A workflow must reject malformed spec Markdown before merge or publication.
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.
Workflow
- Read
references/spec-contract.mdnow — it is the only source for paths, headings, fields, and limits. Do not skip this step. What to read in the codebase is owned by the calling agent. - Write Markdown files that follow that contract. Do not treat them as complete until the validator below has accepted them (or command execution is unavailable).
- When command execution is available, validate from this skill's directory. Pass the specs directory as
--dir(consumer defaultdocs/specs):
node scripts/spec-docs.mjs --dir /path/to/docs/specs
Treat a nonzero validator exit as invalid output and fix the files rather than ignoring the errors. Prompt compliance is advisory; the validator is the enforcement boundary.
Done When
- The validator script accepts the spec directory without errors.
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.
- 2d ago First seen · 35 lines · 64 tokens per session scan A c891aa550c81
spec-reporting is a skill published in the GitHub repository ALTEN-group/coding-pal (2 stars, last pushed 2d ago), licensed MIT. It adds 64 tokens to every session and 346 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…