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 skills add event4u-app/agent-config --skill forensics-reportgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/forensics-report)<a href="https://agentmods.dev/skills/event4u-app/agent-config/forensics-report"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/forensics-report/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/skills/event4u-app/agent-config/forensics-report"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/forensics-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 40 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 52 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00044 | $0.01209 |
| Opus 5 | $0.00022 | $0.00605 |
| Sonnet 5 | $0.00009 | $0.00242 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
forensics-report 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 9d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
forensics-report
When to use
- Before or during a release review, when machine-derived evidence is wanted alongside the human review: "which files are the risk hotspots in this release", "what changes together", "release forensics".
- When intended module boundaries should be checked against what the git history actually shows (change-coupling across module lines).
- The output is advisory, never a gate — it points reviewers at places worth attention; it never passes or fails anything.
- NOT for IT-security incident forensics (route to
incident-commander) and NOT for runtime performance hotspots (route toperformance-analysis).
Procedure
-
Pick the range — the previous release tag to HEAD (
vPREV..HEAD) or a released pair (vPREV..vNEW). Pin the range explicitly; a floating range breaks determinism. -
Run the report:
npx tsx node_modules/@event4u/agent-config/src/scripts/forensics_report.ts --range vPREV..vNEW --out report.jsonTwo deterministic, git-log-based analyzers run, read-only and offline:
- Hotspot risk = normalized change frequency x normalized complexity per file over the range.
- Change-coupling =
co_changes(A,B) / min(changes(A), changes(B))per file pair.
-
Optionally feed the release findings ledger: add
--findings-out findings.json, then ingest vianpx tsx node_modules/@event4u/agent-config/src/scripts/check_finding_dispositions.ts --ingest findings.json --release X.Y.Zwhich appends to the existing ledger at
agents/evidence/release-findings/<version>.json. Emitted findings arekind: correctnesswithseverity: low|medium— non-blocking for the release gate by construction. -
Read the results:
hotspots[]— a hotspot is a place for reviewer attention, NEVER a quality verdict. A frequently changed complex file can be exactly right as it is; the score says "look here", not "this is bad".coupling[]— file pairs that habitually change together.boundary_contradictions[]— cross-module coupling above the threshold, i.e. a contradiction between intended and actual boundaries. This is a finding CLASS to discuss, not a failure.
What ships with it
1 file 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.
- 9d ago First seen · 115 lines · 44 tokens per session scan A 8baa6cb659a2
forensics-report is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,209 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-09-03.
Other skills, from other repositories
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
odh-llm-d-release
Orchestrate the opendatahub-io release for all llm-d components in one cycle. Collects upstream(llm-d) versions, auto-discovers the release tracker issue, then spawns parallel sub-agents — one per component (release branch, Konflux onboarder workflow, PR validation, approve+merge, Quay image verify, GitHub draft…
pr-jira-linker
Find and link Jira issues to PRs/MRs that are missing Jira references. Supports single PR/MR linking and batch audit of configured repos. Use when the user mentions "link PR to Jira", "scan PRs", "PR audit", "MR missing Jira", "link merge request", or wants to connect code changes to Jira for traceability.
gist-upload
Use this skill to upload a summary or plan from the current conversation as a GitHub Gist using the gh CLI.
appstore-archive-uploader
App Store IPA/PKG archives: set version/build numbers, archive, export, upload, or publish with asc xcode before TestFlight/App Store submission.
vllm-backport-push-report
Push a triage report to GitHub under a timestamped directory in reports/. Use after the agent writes the report markdown and has ranked.json ready. Outputs the report URL to stdout.