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/fernandoabolafio/repobase/commitgit clone --depth 1 https://github.com/fernandoabolafio/repobaseWhat 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.00201 |
| Opus 5 | $0.00000 | $0.00101 |
| Sonnet 5 | $0.00000 | $0.00040 |
| Haiku 4.5 | $0.00000 | $0.00020 |
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
- Commit the changes if any with your best knowledge of what the commit should be
If you're unsure what the changes are - run a git diff to see what's in the workbench
Use conventional commits, following:
"@semantic-release/commit-analyzer", { "preset": "conventionalcommits", "releaseRules": [ { "type": "feat", "release": "minor" }, { "type": "fix", "release": "patch" }, { "type": "perf", "release": "patch" }, { "type": "refactor", "release": "patch" }, { "type": "docs", "release": false }, { "type": "style", "release": false }, { "type": "chore", "release": false }, { "type": "test", "release": false }, { "type": "ci", "release": false }, { "breaking": true, "release": "major" } ] }
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 · 23 lines · 0 tokens per session scan A 1ee5325e20ee
commit is a command published in the GitHub repository fernandoabolafio/repobase (16 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 201 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
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
everme-help
Print a concise EverMe plugin status + reference card.
release
Walk the llmwiki release process step by step.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
cost-tracker
Track session costs, understand token spend, and get optimization tips.