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/audit-reportingnpx skills add ALTEN-group/coding-pal --skill audit-reportinggit 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/audit-reporting)<a href="https://agentmods.dev/skills/alten-group/coding-pal/audit-reporting"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/audit-reporting.svg" alt="Measured on agentmods" 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 | $0.00054 | $0.00460 |
| Opus 5 | $0.00027 | $0.00230 |
| Sonnet 5 | $0.00011 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
audit-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 3d 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
Audit Reporting
Produce audit findings that automated workflows can validate and publish safely.
When to Use This Skill
- An audit agent must return deterministic, validated Markdown findings.
- A CI workflow must publish AI findings to an issue or artifact safely.
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 e.g. .github/skills/audit-reporting/ or .copilot/skills/audit-reporting/, use that base path.
Workflow
- Read
references/report-contract.mdnow — it is the only source for markers, sections, fields, limits, and empty-report shape. Do not skip this step. Scope examination and layer review are owned by the calling agent. - Draft a report that follows that contract. Do not treat the draft as published until the validator below has accepted it (or command execution is unavailable).
- When command execution is available, validate and normalize from this skill's directory:
node scripts/audit-report.mjs --input /path/to/raw-audit.md --output /path/to/audit.md --scope src --scope db/liquibase
Treat a nonzero validator exit as an invalid report and regenerate rather than publishing raw output. Prompt compliance is advisory; the validator is the enforcement boundary.
4. After a zero validator exit, read the normalized output file and print its full contents verbatim as the final response. Do not summarize, do not cite the file path, do not write a narrative instead. The CI pipeline reads stdout; it cannot read /tmp/ or any other path you wrote.
Done When
- The validator script accepts the report without errors.
- The accepted report has been printed verbatim in the final response.
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.
- 3d ago First seen · 37 lines · 54 tokens per session scan A 9e0106437d5c
audit-reporting is a skill published in the GitHub repository ALTEN-group/coding-pal (2 stars, last pushed 3d ago), licensed MIT. It adds 54 tokens to every session and 460 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…