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.
git clone --depth 1 https://github.com/cveralyon/axel-setupWrote 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/cveralyon/axel-setup/create-pr)<a href="https://agentmods.dev/commands/cveralyon/axel-setup/create-pr"><img src="https://agentmods.dev/badge/commands/cveralyon/axel-setup/create-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/cveralyon/axel-setup/create-pr"><img src="https://agentmods.dev/badge/commands/cveralyon/axel-setup/create-pr.svg" alt="Reviewed on agentmods" width="80" 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.00187 |
| Opus 5.5 | $0.00000 | $0.00075 |
| Sonnet 5.5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
create-pr 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 1mo 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
Create a Pull Request
- Check that I'm in a branch other than
main,staging, orprod. If not, bail and explain. - Run
git statusto see all changes - If there's unstaged or staged work that hasn't been committed, commit all relevant code first
- Follow commit format:
<tipo> (Modelo/Archivo): Mensaje descriptivo - Max 6 files per commit, grouped by model/functionality
- Follow commit format:
- Use
gh pr createto open a PR with:- Title:
<feature_area>: <Title>(80 chars or less) - Body: TLDR (2 sentences max) + 1-3 bullet points explaining what's changing
- Title:
- Always paste the PR link in the response
- Prepend
GIT_EDITOR=trueto git commands to avoid blocking - NEVER use
--no-verify
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.
- 1mo ago First seen · 14 lines · 0 tokens per session scan A a1cd40bb9baf
create-pr is a command published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 187 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-31.
Other commands, from other repositories
release
Run the weekly release checklist (triage, CHANGELOG, semver tag, GitHub Release, dev.to, LinkedIn, ufawkes.dev) and file the post-release DORA issue.
ship
Run pre-commit, fix issues, commit, push, and open a PR.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.