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/LeanAndMean/scramjetWrote 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/leanandmean/scramjet/mach12-find-contribution-guidelines)<a href="https://agentmods.dev/commands/leanandmean/scramjet/mach12-find-contribution-guidelines"><img src="https://agentmods.dev/badge/commands/leanandmean/scramjet/mach12-find-contribution-guidelines/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/leanandmean/scramjet/mach12-find-contribution-guidelines"><img src="https://agentmods.dev/badge/commands/leanandmean/scramjet/mach12-find-contribution-guidelines.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.00009 | $0.00552 |
| Opus 5 | $0.00005 | $0.00276 |
| Sonnet 5 | $0.00002 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
mach12:find-contribution-guidelines 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 3d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Contribution Guidelines
Goals
- Give the caller a concise, source-grounded summary of all applicable contribution and release guidance.
- Preserve documented requirements, fallback evidence, conflicts, and meaningful omissions without inventing policy or making decisions for the caller.
Step 1: Locate authoritative guidance
Inspect all applicable conventional contribution guidance and repository-local release instructions, rather than stopping after the first file found. Include release material directly referenced by those files.
Keep discovery bounded to conventional guidance locations and their direct references. Do not recursively crawl documentation, infer policy from release history, or search for a repository-specific filename inventory.
Treat contribution and release guidance as primary authority. Only when that authority is absent or leaves a material detail unspecified, inspect nearby project scripts, commands, manifests, and tracked metadata for evidence. Evidence can reveal a missing detail but must not silently override guidance or invent policy.
If neither guidance nor fallback evidence exists, return that no applicable guidance was found.
Step 2: Extract relevant requirements
Read every located authority and identify:
- Project layers: conceptual layers relevant to planning and implementation coverage.
- Testing expectations: frameworks, required test types, coverage rules, and verification commands.
- Pre-merge and release requirements: version declarations and mirrors, generation or synchronization commands, consistency checks, changelog and documentation updates, and lint or format gates.
- Development tooling: documented build, lint, format, schema or artifact validation, generation, compiler/typecheck, and repository-specific verification commands. When the evidence establishes it, report each tool's authority, required or advisory relevance, and mutating or non-mutating effects.
- Issue conventions: templates, label taxonomy, required fields, and shaping rules.
- Other guidance: anything else material to the caller's planning, implementation, review, or release work.
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.
- 3d ago Changed · +6 lines · -1 tokens per session a11f44f54d4b
- 8d ago First seen · 42 lines · 10 tokens per session scan A ad7bff5ca5ba
mach12:find-contribution-guidelines is a command published in the GitHub repository LeanAndMean/scramjet (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 9 tokens to every session and 552 once invoked, about $0.0000 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 commands, from other repositories
computer
Drive a computer's screen, mouse, and keyboard.
afsr
Review feature spec - improve the spec itself before implementation (shortcut for feature-spec-review).
aigon-feedback-triage
Run a triage loop for one feedback item with explicit human confirmation before writes.
add-to-context
Promote reviewed journal facts into context/project/ (propose, then apply).
aigon-feature-spec-review
Review the feature spec itself, not the code. Edit the spec in place using the shared rubric below, then commit the reviewed spec with a spec-review: commit.
aigon-feature-autonomous-start
Start a feature in autonomous mode with explicit agent/evaluator choices and stop point control.