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 nikolai-vysotskyi/trace-mcp --skill trace-mcp-pre-commitgit clone --depth 1 https://github.com/nikolai-vysotskyi/trace-mcpWrote 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/nikolai-vysotskyi/trace-mcp/trace-mcp-pre-commit)<a href="https://agentmods.dev/skills/nikolai-vysotskyi/trace-mcp/trace-mcp-pre-commit"><img src="https://agentmods.dev/badge/skills/nikolai-vysotskyi/trace-mcp/trace-mcp-pre-commit/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/nikolai-vysotskyi/trace-mcp/trace-mcp-pre-commit"><img src="https://agentmods.dev/badge/skills/nikolai-vysotskyi/trace-mcp/trace-mcp-pre-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.00514 |
| Opus 5 | $0.00025 | $0.00257 |
| Sonnet 5 | $0.00010 | $0.00103 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
trace-mcp-pre-commit 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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- trace-mcp-pre-commit — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
trace-mcp — Pre-Commit & Pre-PR Checks
Before creating a commit or opening a pull request, run the trace-mcp validation suite. Fix any critical or high findings before committing.
When to Use
- The user asks to commit, stage, or push changes
- The user asks to open a PR
- The agent has finished implementing a feature or fix and is about to hand off
Checklist
1. Security scan
scan_security({ rules: ["all"] })
OWASP Top-10 vulnerability scan across the changed scope. If the change touches untrusted data flows, add:
taint_analysis({})
Trace untrusted sources to sensitive sinks (SQL, shell, file system, HTTP).
2. Quality gates on the changed scope
check_quality_gates({ scope: "changed" })
Validates complexity, coverage, duplication, and any project-configured gates on only the files you changed.
3. Antipattern scan
detect_antipatterns({})
Flags N+1 queries, eager loading, inefficient iteration, and language-specific performance footguns.
4. Symbol-level diff for the PR description
compare_branches({ branch: "current" })
Produces a symbol-level diff (functions added/removed/modified, signatures changed, exports changed). Use this as the basis for an accurate PR description instead of a raw line diff.
5. Bug prediction (optional, for risky changes)
predict_bugs({})
get_risk_hotspots({})
Flags files where the combination of high complexity and high churn makes regressions likely. If your change touches a hotspot, add extra tests.
Fix or Escalate
- Critical / High findings: fix before committing. Do not suppress without discussion.
- Medium findings: fix if cheap, otherwise note in the PR description.
- Low / Info findings: note in the PR description.
After Commit
If the commit is part of a larger series, consider:
get_changed_symbols({ since: "<base-ref>" })
to generate an accurate changelog entry grounded in the symbol graph rather than commit messages.
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.
- 10d ago First seen · 80 lines · 50 tokens per session scan A 6c0357944955
trace-mcp-pre-commit is a skill published in the GitHub repository nikolai-vysotskyi/trace-mcp (175 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 514 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-30.
Other skills, from other repositories
sem
Use sem to get entity-level (function/class/method) semantic diffs, impact analysis, blame, and dependency context from any Git repo. Trigger this skill whenever the user asks what changed in a commit or PR, wants to understand the blast radius of a change, needs to know who last modified a function, wants to trace…
sem
Semantic version control CLI. Entity-level diffs for Git (functions, classes, methods instead of lines).
coding-agents-farm
To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
m1nd-operator
Use when the user mentions m1nd or when repo investigation, search, review, docs/spec work, or risky change prep should go through m1nd first before grep, glob, or manual file reads. Covers m1nd-first routing, L1GHT and universal document ingestion, risky edit preparation, document-to-code binding, the served owner +…
m1nd-first
Use when investigating a repository, searching for implementation, reviewing changes, working from specs/docs, or preparing a risky code change in an environment where m1nd is available. This doctrine makes m1nd the first investigative layer before grep, glob, or manual file reads, except when the task is pure…
status
Show a comprehensive project status dashboard: task queue, blocked items, session state, verification, and git status.