Borrowing it
Nothing to install: this file belongs to PierreJanineh/TechDebtMCP. 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/PierreJanineh/TechDebtMCP/develop/.claude/skills/add-config-block/SKILL.mdgit clone --depth 1 https://github.com/PierreJanineh/TechDebtMCPWrote 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/pierrejanineh/techdebtmcp/add-config-block)<a href="https://agentmods.dev/skills/pierrejanineh/techdebtmcp/add-config-block"><img src="https://agentmods.dev/badge/skills/pierrejanineh/techdebtmcp/add-config-block/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/pierrejanineh/techdebtmcp/add-config-block"><img src="https://agentmods.dev/badge/skills/pierrejanineh/techdebtmcp/add-config-block.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.00041 | $0.01309 |
| Opus 5 | $0.00020 | $0.00655 |
| Sonnet 5 | $0.00008 | $0.00262 |
| Haiku 4.5 | $0.00004 | $0.00131 |
Grade A, and why
add-config-block 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a Config Block
The .techdebtrc.json schema has a recurring failure mode (filed under TEC-52 umbrella, instances TEC-49 / 56 / 57 / 58): a key is added to VALID_CONFIG_KEYS and validated cleanly, but no code in analysisEngine.ts / baseAnalyzer.ts ever reads it. The validator passes, the user thinks the config works, and the block is silently dead.
This skill enforces the full contract for adding a config block. If any of the 4 steps is skipped, the block is dead config.
The contract
Adding a config key X means all four of the following must land in the same PR:
| Step | File | What |
|---|---|---|
| 1 | src/types/index.ts (TechDebtConfig) |
Add X?: <type> to the interface |
| 2 | src/server/configValidator.ts |
Add 'X' to VALID_CONFIG_KEYS + a validateXField() function |
| 3 | src/core/analysisEngine.ts or src/analyzers/baseAnalyzer.ts |
Read mergedConfig.X and let it influence output |
| 4 | tests/fixtures/self-scan/X/ + src/core/__tests__/selfScan.test.ts assertion |
Fixture project whose output differs with and without the block |
Step 4 is the load-bearing one. The self-scan test is what catches the "validated but never consumed" bug class — if the assertion can't tell the difference between "X is set" and "X is omitted," the consumer in step 3 isn't doing anything.
Procedure
1. Brainstorm the semantics first
Before touching code: write down on paper (or in the PR description draft) the observable effect of the block. Examples:
severity— "an issue's emitted severity is overridden when itsrulematches a key inconfig.severity"include— "files matching noincludeglob are excluded from analysis"languageOverrides— "language-specific config (e.g. extensions, patterns) is replaced/extended per language"
If you can't state the effect in one sentence, stop. The block is not well-defined yet — that's a brainstorming task, not an implementation task.
2. Extend the type
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 · 91 lines · 41 tokens per session scan A 9b1071b08672
add-config-block is a skill published in the GitHub repository PierreJanineh/TechDebtMCP (7 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,309 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-08-31.
Other skills, from other repositories
prompt-optimization
Improves LLM-facing context while preserving intent, execution boundaries, and proportional work. Use when creating or reviewing prompts, agent definitions, skill definitions, or other instructions for an LLM.
recipe-eval-prompt
Compares original and optimized prompts through repeated blind paired execution in git worktrees. Use when evaluating prompt improvement effects or learning prompt engineering through concrete examples.
knowledge-base
Retrieves and updates project-specific prompt knowledge from comparison evidence and user feedback. Use only for prompt analysis or post-comparison learning within a Rashomon evaluation.
worktree-execution
Creates, pins, and cleans isolated Git worktree pairs for comparison trials. Use only when a Rashomon prompt or skill evaluation needs paired execution environments or orphan recovery.
interview-me
Deep-dive spec interviewer. Reads a file, GitHub issue, or requirement, analyzes it against the codebase, then conducts a rigorous 1-on-1 interview using AskUserQuestion to produce a comprehensive, opinionated specification document. Acts as a collaborative architect with active pushback. Also runs --verify to detect…
codecartographer
Drive the CodeCartographer MCP server to reverse-engineer a repository or synthesize a new project through validated analysis phases. Use when asked to run CodeCartographer, analyze or reverse-engineer a codebase, produce architecture/contracts/protocols/defect/porting/reimplementation artifacts, or operate a…