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 commands/richard-luc/kicad-schematic-manipulation/dead-code-analysisgit clone --depth 1 https://github.com/richard-luc/KiCAD-Schematic-ManipulationWrote 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/commands/richard-luc/kicad-schematic-manipulation/dead-code-analysis)<a href="https://agentmods.dev/commands/richard-luc/kicad-schematic-manipulation/dead-code-analysis"><img src="https://agentmods.dev/badge/commands/richard-luc/kicad-schematic-manipulation/dead-code-analysis.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.00000 | $0.01702 |
| Opus 5 | $0.00000 | $0.00851 |
| Sonnet 5 | $0.00000 | $0.00340 |
| Haiku 4.5 | $0.00000 | $0.00170 |
Grade A, and why
dead-code-analysis 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 4d 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.
This is a copy
95% identical to dead-code-analysis — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dead Code Analysis Command - kicad-sch-api
Usage
/dead-code-analysis [target-script]
Description
Performs comprehensive dead code analysis for kicad-sch-api by running ALL functionality and observing which functions are actually called. This provides accurate utilization metrics by exercising:
- Core Schematic Operations - Load, save, component management, validation
- S-Expression Parsing - All parsing and formatting functionality
- Component Collections - Filtering, bulk operations, indexing
- Symbol Library Management - Caching, discovery, multi-source lookup
- MCP Server Integration - All MCP tools and Python bridge
- Validation Systems - Error collection, comprehensive validation
- Format Preservation - Round-trip testing, exact output matching
- Performance Systems - Caching, optimization, benchmarking
Parameters
target-script(optional): Path to script to run for function call analysis. Defaults to comprehensive test suite.--comprehensive: Runs full system functionality test (default behavior)
Output Files
function_calls.log: Raw debug output from script executionunique_function_calls.txt: List of unique functions that were calledDead_Code_Analysis_Report.md: Comprehensive analysis report*.backup: Backup files for all instrumented source files
Examples
# Analyze dead code using comprehensive test suite
/dead-code-analysis
# Analyze using specific test script
/dead-code-analysis tests/test_comprehensive_operations.py
# Analyze using MCP server test
/dead-code-analysis tests/test_mcp_integration.py
Implementation for kicad-sch-api
The command performs the following automated steps:
1. Function Instrumentation
- Scans all Python files in
kicad_sch_api/ - Adds
logging.debug(f"CALLED: {function_name} in {file_path}")to every function - Creates backup files (
.backup) before modification - Preserves existing function logic and formatting
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.
- 4d ago First seen · 220 lines · 0 tokens per session scan A 48825f887ab3
dead-code-analysis is a command published in the GitHub repository richard-luc/KiCAD-Schematic-Manipulation (0 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,702 tokens. A static security scan graded it A with 0 findings. It is 95% identical to dead-code-analysis, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
review-branch
Purpose: Comprehensive branch analysis for code quality, security, performance, and risk assessment before merging to main. Specialized for circuit-synth development workflows.
dead-code-analysis
Command "dead-code-analysis" from circuit-synth/circuit-synth, covering dead code analysis command, usage, description, parameters and output files.
bug
Debug and fix issues with log-driven iterative approach.
make-test
Wrap manual test into automated pytest test.
review-prompt
Review prompts for best practices and clarity.
test-ref
Create reference material for testing and development.