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/sollawen/microneo/commitnpx skills add sollawen/microNeo --skill commitgit clone --depth 1 https://github.com/sollawen/microNeoWhat 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.00017 | $0.00360 |
| Opus 5 | $0.00009 | $0.00180 |
| Sonnet 5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
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.
What it actually says
Usage
This is a rules document for the assistant to follow. When the user says "commit", load these rules and execute the commit directly—do not summon another assistant.
Rules
Principles
- Only commit when the user literally says "commit" (or gives an unambiguous commit instruction like "提交" / "commit this"). Approving a plan, choosing a value, or saying "ok / 就这样 / go ahead / do it" about a code change is NOT commit permission — apply the edit, then stop and wait for the explicit word.
- Never auto-commit.
- When in doubt, make the edit and ask before committing.
- When user says "commit all", stage and commit all modified files together in one commit.
- Do NOT push after commit. Leave that to the user.
- When the commit involves user-visible code changes or a significant internal refactor, use the
changelogskill to update the[Unreleased]section ofCHANGELOG.md, then commit the changelog update together with the code in the same commit. Skip this for puredocs:/chore:commits and trivial refactors.
Requirements
title
- title of the commit MUST Use English
- Follow GitHub conventional commit prefixes:
feat:,fix:,docs:,style:,refactor:,perf:,test:,chore:, etc.
message body
- Mix Chinese and English
- Technical terms in English (e.g.,
PR,branch,commit,merge)
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 · 32 lines · 17 tokens per session scan A 755a7835ade9
commit is a skill published in the GitHub repository sollawen/microNeo (55 stars, last pushed 15d ago), licensed MIT. It adds 17 tokens to every session and 360 once invoked, about $0.0001 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-30.
Other skills, from other repositories
write-documentation
Write and format Rust documentation correctly. Apply proactively when writing code with rustdoc comments (//! or ///). Covers voice & tone, prose style (opening lines, explicit subjects, verb tense), structure (inverted pyramid), intra-doc links (crate:: paths, reference-style), constant conventions (binary/byte…
organize-modules
Apply private modules with public re-exports (barrel export) pattern for clean API design. Includes conditional visibility for docs and tests. Use when creating modules, organizing mod.rs files, or before creating commits.
check-bounds-safety
Apply type-safe bounds checking patterns using VPIndex/VPLength types instead of usize. Use when working with arrays, buffers, cursors, viewports, or any code that handles indices and lengths.
check-code-quality
Run comprehensive Rust code quality checks including compilation, linting, documentation, and tests. Use after completing code changes and before creating commits.
analyze-performance
Establish performance baselines and detect regressions using flamegraph analysis. Use when optimizing performance-critical code, investigating performance issues, or before creating commits with performance-sensitive changes.
run-clippy
Run clippy linting, enforce comment punctuation rules, format code with cargo fmt, and verify module organization patterns. Use after code changes and before creating commits.