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/circuit-synth/kicad-sch-api/update-and-commitgit clone --depth 1 https://github.com/circuit-synth/kicad-sch-apiWhat 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.01486 |
| Opus 5 | $0.00000 | $0.00743 |
| Sonnet 5 | $0.00000 | $0.00297 |
| Haiku 4.5 | $0.00000 | $0.00149 |
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 2d 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
2 near-identical copies found in the catalogue:
- update-and-commit — 89% identical, 30 lines differ
- update-and-commit — 89% identical, 30 lines differ
How it starts
The opening of the file, as written. The whole thing — 201 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 (REQUIRED for Features)
IMPORTANT: Always update documentation BEFORE committing new features
- IF new user-facing features: Update README.md with examples
- IF new API methods: Add to Advanced Features section in README.md
- IF version increment needed: Update CHANGELOG.md with new version entry
- IF new MCP tools: Update tool documentation
- ALWAYS document new public methods with code examples
- NO documentation changes needed for internal fixes or refactoring
# Documentation update checklist for new features:
# 1. Add examples to README.md "Basic Usage" or "Advanced Features" sections
# 2. Create CHANGELOG.md entry with version bump (patch/minor/major)
# 3. Update any relevant example files in examples/
# 4. Ensure CLAUDE.md reflects new functionality if developer-relevant
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"
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.
- 2d ago First seen · 201 lines · 0 tokens per session scan A b54fa55841b8
update-and-commit is a command published in the GitHub repository circuit-synth/kicad-sch-api (51 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,486 tokens. 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 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".
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.