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/thewaywithin/agent-11/reportgit clone --depth 1 https://github.com/TheWayWithin/agent-11Wrote 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/thewaywithin/agent-11/report)<a href="https://agentmods.dev/commands/thewaywithin/agent-11/report"><img src="https://agentmods.dev/badge/commands/thewaywithin/agent-11/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.1 | $0.00007 | $0.00729 |
| Opus 5 | $0.00003 | $0.00365 |
| Sonnet 5 | $0.00001 | $0.00146 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
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 yesterday.
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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PROGRESS REPORT GENERATION 📊
Command: /report [since_date]
Purpose: Generate a structured progress report documenting completed tasks, issues encountered, and project status for external stakeholders (BOS-AI, clients, or management).
KEY FEATURES
- Automated Data Collection: Pulls from project-plan.md, progress.md, and git history
- Time-Based Reporting: Reports changes since last report or specified date
- Stakeholder-Ready Format: Professional structure suitable for external communication
- BOS-AI Integration: Special sections when integrated with BOS-AI documents
- Issue Tracking: Documents problems encountered and their resolutions
USAGE EXAMPLES
# Generate report for last 7 days (default)
/report
# Generate report since specific date
/report 2025-08-20
# Generate report since last report (automatic detection)
/report
REPORT SECTIONS
1. Executive Summary
Brief overview of progress and current status
2. Tasks Completed
Table of completed tasks with dates and business impact
3. Issues & Resolutions
Documentation of problems encountered and how they were resolved
4. Current Status
Overall project health and active phase
5. Metrics
Key performance indicators and trends
6. Next Milestones
Upcoming deliverables and target dates
7. Resource Needs
Decisions, resources, or clarifications needed from stakeholders
8. Business Alignment (BOS-AI Integration)
How development aligns with business vision and requirements
OUTPUT
Generates progress-report.md with:
- Structured markdown format
- Tables for easy scanning
- Visual indicators (✅, ⚠️, 📈, 📉)
- Clear action items for stakeholders
- Timestamp and next report date
BENEFITS
- Transparency: Clear visibility into development progress
- Accountability: Documented completion and issue resolution
- Communication: Bridge between technical work and business stakeholders
- Tracking: Historical record of project evolution
- Planning: Identifies resource needs and blockers early
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.
- yesterday First seen · 109 lines · 7 tokens per session scan A 6e45626f88ac
report is a command published in the GitHub repository TheWayWithin/agent-11 (15 stars, last pushed 13d ago), licensed MIT. It adds 7 tokens to every session and 729 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-09-04.
Other commands, from other repositories
ensemble:generate-project-router-rules
Generate project-specific router rules by analyzing the project's tech stack.
ensemble:generate-router-rules
Generate router rules by introspecting installed agents and skills.
brainstorm
Facilitate a structured brainstorming session for feature development using Scrum Master techniques.
generate-prp
Generate comprehensive PRP (Product Requirements & Plans) with thorough research and validation.
execute-task
Execute individual development tasks from task breakdown documents.
execute-prp
Implement features from PRP specifications with comprehensive validation and testing.