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 skills/agentconfig/agentconfig.org/semantic-commitnpx skills add agentconfig/agentconfig.org --skill semantic-commitgit clone --depth 1 https://github.com/agentconfig/agentconfig.orgWhat 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.00037 | $0.00824 |
| Opus 5 | $0.00018 | $0.00412 |
| Sonnet 5 | $0.00007 | $0.00165 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
semantic-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 yesterday.
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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semantic Commit
Create clean, semantic git commits following strict commit discipline.
Commit Format
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
Types
| Type | When to Use |
|---|---|
feat |
New feature or functionality |
fix |
Bug fix |
docs |
Documentation changes only |
style |
Formatting, whitespace (no code logic change) |
refactor |
Code restructuring without behavior change |
test |
Adding or updating tests |
chore |
Maintenance, configs, dependencies |
Scopes (Project-Specific)
Common scopes for agentconfig.org:
file-tree- FileTree component/visualizationcards- PrimitiveCards componentcomparison- ProviderComparison componenthero- Hero sectionnavigation- Navigation componenttheme- ThemeProvider, ThemeToggle, dark/light modedata- Data files in site/src/data/e2e- Playwright testsskills- Skill files in .github/skills/
Rules
1. Atomic Commits
Each commit must represent ONE logical change. If you're tempted to use "and" in your description, split it into multiple commits.
# Bad
feat(ui): add file tree component and update navigation
# Good - Two separate commits
feat(file-tree): add collapsible tree node component
fix(navigation): update scroll offset for new header
2. Minimize Files
Prefer multiple small commits over one large commit. Ask: "Can this be split further?"
3. Clear Descriptions
The description should complete: "This commit will..."
- Use imperative mood: "add", "fix", "update" (not "added", "fixes")
- Be specific but concise
- No period at the end
4. Pre-Commit Verification
Before committing, verify:
bun run lintpassesbun run typecheckpassesbun run testpasses- Only intended files are staged
- No debug code or console.logs (unless intentional)
Workflow
When asked to commit:
- Review changes with
git statusandgit diff --staged - Assess scope - Determine if this should be one or multiple commits
- Unstage if needed - If changes span multiple features, commit separately
- Write message following the format
- Verify - Run lint, typecheck, and tests
- Commit only after verification passes
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.
- yesterday First seen · 123 lines · 37 tokens per session scan A 6d44002ea5fc
semantic-commit is a skill published in the GitHub repository agentconfig/agentconfig.org (7 stars, last pushed 4d ago), licensed ISC. It adds 37 tokens to every session and 824 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
clinical-reports
Write comprehensive clinical reports including case reports (CARE guidelines), diagnostic reports (radiology/pathology/lab), clinical trial reports (ICH-E3, SAE, CSR), and patient documentation (SOAP, H&P, discharge summaries). Full support with templates, regulatory compliance (HIPAA, FDA, ICH-GCP), and validation…
clinical-decision-support
Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading…
molecular-cloning
Molecular cloning simulation and design. PCR amplicon prediction, restriction enzyme digestion, Golden Gate and Gibson assembly simulation, primer design, CRISPR sgRNA design, and plasmid annotation. For protein-level sequence analysis use biopython or esm; for database lookups use gene-database or ensembl-database.
bioimage-analysis
Microscopy image analysis for cell biology. Cell segmentation (Cellpose, watershed), object tracking (trackpy), morphology quantification, colony counting, colocalization analysis, and cytoskeleton characterization. For pathology WSI use pathml; for flow cytometry use flow-cytometry-analysis.
flow-cytometry-analysis
Complete flow cytometry analysis pipeline. FCS file handling, compensation, manual/automated gating, immunophenotyping, CFSE proliferation analysis, cell cycle analysis (Dean-Jett-Fox), and apoptosis assays. Extends flowio with analytical workflows. For raw FCS parsing only use flowio.
immunology-assays
Computational analysis of immunology experimental data. ATAC-seq differential accessibility, immune cell tracking from microscopy, ELISA data processing with 4-parameter logistic fitting, immunohistochemistry quantification, antibody titer analysis, and cell cycle phase duration estimation. For flow cytometry use…