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/dep/agent-rules/report-enhancementgit clone --depth 1 https://github.com/dep/agent-rulesWrote 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/dep/agent-rules/report-enhancement)<a href="https://agentmods.dev/commands/dep/agent-rules/report-enhancement"><img src="https://agentmods.dev/badge/commands/dep/agent-rules/report-enhancement.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.00000 | $0.00121 |
| Opus 5 | $0.00000 | $0.00060 |
| Sonnet 5 | $0.00000 | $0.00024 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
REPORT-ENHANCEMENT 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.
What it actually says
Report a Feature Enhancement
Overview
A feature enhancement request has come in from a customer and your task is to create a github issue for tracking the feature request. If a feature request is already created for the request, add a "+1" comment on the existing issue to indicate that it's being requested again.
Process
- Gain an understanding of the feature request
- Use the Github MCP server to find any existing issues for this request
- If one exists, add a "+1" comment on it, if not, create a new feature request issue using the MCP server
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 First seen · 9 lines · 0 tokens per session scan A ed1294c078c7
REPORT-ENHANCEMENT is a command published in the GitHub repository dep/agent-rules (11 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 121 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-30.
Other commands, from other repositories
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).