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/cameronfreer/lean4-skills/bug-reportgit clone --depth 1 https://github.com/cameronfreer/lean4-skillsWrote 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/cameronfreer/lean4-skills/bug-report)<a href="https://agentmods.dev/commands/cameronfreer/lean4-skills/bug-report"><img src="https://agentmods.dev/badge/commands/cameronfreer/lean4-skills/bug-report.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.01026 |
| Opus 5 | $0.00006 | $0.00513 |
| Sonnet 5 | $0.00003 | $0.00205 |
| Haiku 4.5 | $0.00001 | $0.00103 |
Grade A, and why
bug-report 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 4d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Report
Draft and submit a bug report as a GitHub issue on cameronfreer/lean4-skills.
Precondition
Invoke this command only if the user explicitly ran it or explicitly agreed to draft a bug report. If invoked without prior opt-in, ask:
This looks like a lean4-skills bug. Want me to draft a bug report?
If the user explicitly ran /lean4-contribute:bug-report, treat that as opt-in.
Do not proceed unless the user confirms. Do not mine git diff, gather
diagnostics, or ask structured questions until consent is given.
Gathering Context
Collect the following from the user and the current session. Ask for anything you cannot infer:
- Summary — One-line description of the bug
- Expected behavior — What should happen
- Actual behavior — What happens instead
- Repro steps — Numbered steps to reproduce
- Minimal Lean snippet — Smallest code that triggers the bug (strip project-specific details)
- Environment / toolchain — Lean version (
lean --version), lake version, OS, plugin version, relevant MCP servers - Diagnostics / build output — Compiler errors, lake build output, or LSP messages (redact paths and usernames)
- Possible fix (optional) — If you have a local fix, write a short
prose summary of what the fix does (1–3 sentences). Do not include
a raw diff by default. If the user explicitly asks to include a patch
excerpt, include only the minimal relevant hunk (not the whole diff), strip
file paths and surrounding context, and require a separate confirmation:
This draft includes a code patch. Review it for unrelated code or secrets. Include this patch? (yes / remove it / edit)
- Privacy / redaction check — Before showing the draft, scan for filesystem paths, usernames, API keys, or other sensitive data and redact them. Flag anything you redacted so the user can verify.
Drafting the Issue
Compose the issue using this template:
Title: [Bug] <summary>
Labels: bug
## Summary
<summary>
## Expected Behavior
<expected behavior>
## Actual Behavior
<actual behavior>
## Steps to Reproduce
<numbered repro steps>
## Minimal Example
```lean
<minimal Lean snippet>
Environment
- Lean:
- Lake:
- OS:
- Plugin:
- MCP:
Diagnostics
<build output / compiler errors>
Possible Fix
<prose summary of fix; minimal patch excerpt only if user confirmed>
Drafted via lean4-contribute
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.
- 4d ago First seen · 122 lines · 13 tokens per session scan A 3fe44008451c
bug-report is a command published in the GitHub repository cameronfreer/lean4-skills (428 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 1,026 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.