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 agents/cveralyon/axel-setup/featuregit clone --depth 1 https://github.com/cveralyon/axel-setupWhat 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.00020 | $0.00624 |
| Opus 5 | $0.00010 | $0.00312 |
| Sonnet 5 | $0.00004 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
feature 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold a new feature end-to-end by following the exact patterns in the current repo.
Step 1: Detect project type and audit patterns
- Rails (Gemfile) → DDD service layer pattern
- Next.js (package.json + next.config) → service + hooks + components pattern
- Read 2-3 existing examples of similar features to match conventions exactly
Step 2: Rails (API)
Create in order:
- Types/Model —
app/models/with validations, associations, Paranoia, PaperTrail if needed - Service —
app/services/{domain}/followingNamespace::Actionnaming, single responsibility - Serializer —
app/serializers/for JSON formatting - Controller —
app/controllers/api/v1/thin, delegates to service, RESTful - Routes —
config/routes.rbusing PATCH (not PUT), namespaced - Migration — Only if user confirms. Check timestamp consistency with last migration
- Specs —
spec/matching the created files: model spec, request spec, service spec
Step 3: Next.js (Frontend)
Create in order:
- Types —
services/{domain}/types.tsorlib/types/{domain}.ts - Endpoints —
services/{domain}/endpoints.tswith SCREAMING_SNAKE_CASE - Services —
services/{domain}/servicesClient.ts+servicesServer.ts - Hooks —
hooks/{domain}/use-{feature}.tswith React Query - Components —
components/{domain}/with PascalCase names, kebab-case files - Route —
app/[locale]/(workspace)/{domain}/page.tsx - Translations — Add keys to all 4 locales (en, es, ca, fr)
Rules
- Read existing patterns before creating anything — never assume
- kebab-case files, PascalCase components, SCREAMING_SNAKE_CASE constants
- All code in English, explanations in Spanish
- Ask before creating migrations
- Run validation after:
rubocop/pnpm check
Before scaffolding — de-risk first (escalate when needed)
- If feasibility or an unfamiliar integration is uncertain, recommend a throwaway
gsd-spikebefore committing to the scaffold. - If the UI direction is unsettled, recommend exploring with
gsd-sketch(throwaway HTML mockups) before writing components.
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 · 49 lines · 20 tokens per session scan A b3e10a38735f
feature is an agent published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 624 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-31.
Other agents, from other repositories
syllago-author
/home/hhewett/.local/src/syllago/content/agents/syllago-author/AGENT.md.
feature-flow
Build, test, verify, and review an already planned feature. Operates on a feature branch off trunk; prepares a PR but does not merge.
review
Review PR and build output for quality, security, and compliance. Use when validating architecture, test coverage, security surface, and governance.
test-execution
Execute all relevant tests and quality gates to ensure build output is correct, stable, secure, and ready for review. This is feature-flow's Phase 3 (and Phase 3.5 for live-system verification) — local, pre-push verification. Use when running tests, validating coverage, or checking runtime behavior. Distinct from the…
design
Convert the specification into a clear, actionable technical design with architecture, components, interfaces, and data flows. Use when translating requirements into a buildable system design.
learn
Product retrospective agent. Runs after a release, after a measure agent anomaly flag, or at end of sprint. Maps findings to DORA AI capabilities and produces plan agent action items. Distinct from fawkes learn.md which handles platform incident postmortems.