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/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/feature-request)<a href="https://agentmods.dev/commands/cameronfreer/lean4-skills/feature-request"><img src="https://agentmods.dev/badge/commands/cameronfreer/lean4-skills/feature-request/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/cameronfreer/lean4-skills/feature-request"><img src="https://agentmods.dev/badge/commands/cameronfreer/lean4-skills/feature-request.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.00013 | $0.00836 |
| Opus 5.5 | $0.00005 | $0.00334 |
| Sonnet 5.5 | $0.00003 | $0.00167 |
| Haiku 4.5 | $0.00001 | $0.00084 |
Grade A, and why
feature-request 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Request
Draft and submit a feature request 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 feature request. If invoked without prior opt-in, ask:
This looks like a plugin workflow gap. Want me to draft a feature request?
If the user explicitly ran /lean4-contribute:feature-request, treat that as opt-in.
Do not proceed unless the user confirms. Do not gather structured questions
or build an issue body until consent is given.
Gathering Context
Collect the following from the user and the current session. Ask for anything you cannot infer:
- Problem / pain point — What is frustrating, slow, or missing?
- Current workaround — How do you handle this today? (or "none")
- Desired behavior — What should the plugin do instead?
- Why this belongs in the plugin — Why is this a plugin concern rather than a user-side script or external tool?
- Acceptance criteria — Concrete conditions that would mark this done
- Alternatives considered — Other approaches you thought of and why they fall short
- Urgency / frequency — How often do you hit this? Blocking, frequent annoyance, nice-to-have?
Drafting the Issue
Compose the issue using this template:
Title: [Feature] <short description>
Labels: enhancement
## Problem / Pain Point
<problem description>
## Current Workaround
<workaround or "none">
## Desired Behavior
<what the plugin should do>
## Why This Belongs in the Plugin
<justification>
## Acceptance Criteria
- [ ] <criterion 1>
- [ ] <criterion 2>
- ...
## Alternatives Considered
<other approaches and trade-offs>
## Urgency / Frequency
<how often, how blocking>
---
*Drafted via [lean4-contribute](https://github.com/cameronfreer/lean4-skills)*
Showing the Draft
Display the complete issue draft to the user — title, labels, and full body. Ask:
Here is the feature request I will submit. Review it carefully.
By submitting, you agree that this content may be edited, rearranged, or incorporated into lean4-skills in any form under its MIT license.
Submit this issue? (yes / edit / cancel)
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 · 105 lines · 13 tokens per session scan A 0ef61c86dc61
feature-request is a command published in the GitHub repository cameronfreer/lean4-skills (465 stars, last pushed 19d ago), licensed MIT. It adds 13 tokens to every session and 836 once invoked, about $0.0001 per session on Opus 5.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
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.