Borrowing it
Nothing to install: this file belongs to certinia/debug-log-analyzer-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/certinia/debug-log-analyzer-mcp/main/.claude/skills/repo-docs/SKILL.mdgit clone --depth 1 https://github.com/certinia/debug-log-analyzer-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/certinia/debug-log-analyzer-mcp/repo-docs)<a href="https://agentmods.dev/skills/certinia/debug-log-analyzer-mcp/repo-docs"><img src="https://agentmods.dev/badge/skills/certinia/debug-log-analyzer-mcp/repo-docs/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/certinia/debug-log-analyzer-mcp/repo-docs"><img src="https://agentmods.dev/badge/skills/certinia/debug-log-analyzer-mcp/repo-docs.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00065 | $0.00908 |
| Opus 5.5 | $0.00026 | $0.00363 |
| Sonnet 5.5 | $0.00013 | $0.00182 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
repo-docs 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 17d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo docs
Voice comes from the developer-writing skill. This skill says which file a fact belongs in and
what shape that file expects. Changelog entries have their own rules - use changelog-entry.
One fact, one file
| Fact | File |
|---|---|
| What a tool returns, its parameters, its response fields | README.md, Tools Reference |
| What a 1.x caller must change | MIGRATING.md |
| What a reader of the released package can see changed | CHANGELOG.md (changelog-entry skill) |
| The rules every change follows, and how to build and release | DEVELOPING.md - rules only, no evidence |
| Why code is the way it is: a measurement, a rejected alternative | a doc comment on that code |
| How Salesforce behaves, tested in an org | .claude/rules/<topic>.md, dated, with the issue link; the code links to it |
| What a contributor or agent needs before touching the code | CLAUDE.md |
| Why a budget number is what it is | the comment beside it in scripts/eval.mjs |
Response-shaping policy never reaches the wire: not a .describe(), not a tool description. It is a
contributor fact.
README shape, per tool
The Tools Reference gives each tool, in this order:
- One paragraph of what it answers and what it is best for - the served tool description in README voice, not a copy of it.
- The generated
shape-<tool>block: every response field and its columns. - Hand-written prose for what the block cannot say - what a column means, what makes one conditional, what an extra table joins to.
- The generated
params-<tool>block.
A new parameter regenerates its own row. Write prose for it only if it changes what the rows carry.
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.
- 17d ago Changed · +3 lines c9c036c2375a
- 18d ago Changed · +2 lines f868efbfe9d3
- 2mo ago First seen · 66 lines · 65 tokens per session scan A c130324f5669
repo-docs is a skill published in the GitHub repository certinia/debug-log-analyzer-mcp (36 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 65 tokens to every session and 908 once invoked, about $0.0003 per session on Opus 5.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-07.
repo-docs compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| repo-docscertinia/debug-log-analyzer-mcp | Skill | 36 | 2d ago | BSD-3-Clause | A | 65 | Claude Code |
| opik-diagnosecomet-ml/opik-mcp | Skill | 225 | 9d ago | Apache-2.0 | A | 187 | Claude Code |
| ue-mcp-epic-routingdb-lyon/ue-mcp | Skill | 476 | yesterday | MIT | A | 81 | Claude Code, Codex |
| qa-knowledgegriddynamics/rosetta | Skill | 370 | yesterday | Apache-2.0 | A | 32 | Claude Code, Codex |
| apitapn1byn1kt/apitap | Skill | 131 | 17d ago | Apache-2.0 | A | 0 | Claude Code, Codex |
| frontmcp-setupagentfront/frontmcp | Skill | 148 | yesterday | Apache-2.0 | A | 176 | Claude Code, Codex |
| x-use-reviewihuzaifashoukat/x-use | Skill | 181 | 4d ago | MIT | A | 56 | Claude Code |