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/update-and-commitgit 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/update-and-commit)<a href="https://agentmods.dev/commands/richard-luc/kicad-schematic-manipulation/update-and-commit"><img src="https://agentmods.dev/badge/commands/richard-luc/kicad-schematic-manipulation/update-and-commit.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.1 | $0.00000 | $0.01321 |
| Opus 5 | $0.00000 | $0.00660 |
| Sonnet 5 | $0.00000 | $0.00264 |
| Haiku 4.5 | $0.00000 | $0.00132 |
Grade A, and why
update-and-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 5d 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
89% identical to update-and-commit — 30 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update and Commit Command - kicad-sch-api
Usage
/update-and-commit "Brief description of changes"
Description
Comprehensive workflow for documenting progress, updating documentation, and committing changes to kicad-sch-api with professional quality standards.
Process
1. Update Documentation (Only if Needed)
- IF new user-facing features: Update README.md briefly
- IF new MCP tools: Update tool documentation
- IF new API methods: Update examples in README
- NO documentation changes for internal fixes or refactoring
2. Format Code Before Committing
IMPORTANT: Always format code before committing
# Format Python code
uv run black kicad_sch_api/ tests/ --quiet
uv run isort kicad_sch_api/ tests/ --quiet
# Format TypeScript (MCP server)
cd mcp-server && npm run format --silent 2>/dev/null || echo "TypeScript formatting skipped"
cd ..
# Format configuration files
prettier --write "*.{json,yml,yaml}" --ignore-path .gitignore 2>/dev/null || echo "Config formatting skipped"
3. Quality Checks Before Committing
IMPORTANT: Run basic quality checks
# Syntax validation
find kicad_sch_api/ tests/ -name "*.py" -exec python -m py_compile {} \; 2>/dev/null || echo "⚠️ Syntax errors found"
# Quick test run
uv run pytest tests/test_component_management.py tests/test_sexpr_parsing.py -q || echo "⚠️ Core tests failing"
# Import validation
uv run python -c "import kicad_sch_api; print('✅ Import successful')" || echo "⚠️ Import failed"
4. Commit Changes (Selective and Clean)
IMPORTANT: Keep commit message under 3 lines
# Check status and review changes
git status
# Add specific files (be selective)
git add kicad_sch_api/ tests/ README.md pyproject.toml
# Remove unwanted files if any
git rm unwanted-file.py 2>/dev/null || true
# Commit with professional message
git commit -m "Brief description of change
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <[email protected]>"
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.
- 5d ago First seen · 189 lines · 0 tokens per session scan A 77e685ea5b51
update-and-commit 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,321 tokens. A static security scan graded it A with 0 findings. It is 89% identical to update-and-commit, differing in 30 lines, and is treated as a copy.
Other commands, from other repositories
update-and-commit
Comprehensive workflow for documenting progress and committing changes.
update-and-commit
/update-and-commit "Brief description of changes".
push
You are creating a commit for the user. Follow these steps EXACTLY.
dead-code-analysis
Command "dead-code-analysis" from circuit-synth/circuit-synth, covering dead code analysis command, usage, description, parameters and output files.
review-branch
Purpose: Comprehensive branch analysis for code quality, security, performance, and risk assessment before merging to main. Specialized for circuit-synth development workflows.
title-commit
Stage the files belonging to the current change theme and propose a commit title (does NOT commit).