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/luanmorenommaciel/agentspec/statusgit clone --depth 1 https://github.com/luanmorenommaciel/agentspecWrote 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/luanmorenommaciel/agentspec/status)<a href="https://agentmods.dev/commands/luanmorenommaciel/agentspec/status"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/agentspec/status.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.00021 | $0.01852 |
| Opus 5 | $0.00010 | $0.00926 |
| Sonnet 5 | $0.00004 | $0.00370 |
| Haiku 4.5 | $0.00002 | $0.00185 |
Grade A, and why
status 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 2d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status Report Command
Generates a project status report by scanning the SDD workspace, git history, and codebase health indicators.
Usage
/status # Full project status report
/status "sprint review" # Status with specific context for a sprint review
What It Does
- Scans the SDD workspace for active and recently shipped features
- Checks git state for recent commits, branches, and uncommitted work
- Detects project health (tests, TODOs, documentation, stack)
- Generates actionable recommendations based on current state
Execution Process
Execute all steps inline (no agent delegation) and produce the report directly.
Step 1: Scan SDD Workspace
# Active features
Glob(".claude/sdd/features/BRAINSTORM_*.md")
Glob(".claude/sdd/features/DEFINE_*.md")
Glob(".claude/sdd/features/DESIGN_*.md")
# Build reports
Glob(".claude/sdd/reports/BUILD_REPORT_*.md")
# Recently shipped
Glob(".claude/sdd/archive/*")
For each discovered document:
- Extract the feature name from the filename
- Read the first 10 lines to determine status and last updated date
- Determine the current SDD phase (Brainstorm, Define, Design, Build, Shipped)
- Flag any blockers mentioned in the document
Step 2: Check Git State
# Recent commits
git log --oneline -10
# Uncommitted changes
git status --short
# Current branch
git branch --show-current
# All local branches
git branch
# Check for pending PRs (only if gh CLI is available)
gh pr list --state open --limit 5 2>/dev/null || echo "gh CLI not available"
Step 3: Detect Project Health
# Test files
Glob("**/test_*.py")
Glob("**/*_test.py")
Glob("**/*.test.ts")
Glob("**/*.test.js")
Glob("**/*.spec.ts")
Glob("**/*.spec.js")
Glob("**/tests/**/*.py")
# TODO/FIXME count
Grep("TODO|FIXME", output_mode="count")
# Documentation check
Glob("CLAUDE.md")
Glob("README.md")
# Stack detection via config files
Glob("**/pyproject.toml")
Glob("**/package.json")
Glob("**/dbt_project.yml")
Glob("**/Dockerfile")
Glob("**/*.tf")
Glob("**/airflow.cfg")
Glob("**/requirements.txt")
Glob("**/Cargo.toml")
Glob("**/go.mod")
Glob("**/pom.xml")
# KB domain alignment
Glob(".claude/kb/*/index.md")
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.
- 2d ago First seen · 267 lines · 21 tokens per session scan A 1f4edcfcfb68
status is a command published in the GitHub repository luanmorenommaciel/agentspec (244 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 1,852 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-09-01.
Other commands, from other repositories
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间,成员权限,团队组织.
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).
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.