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/funkyoz/funkyoz-plugins/statusgit clone --depth 1 https://github.com/FunkyOz/funkyoz-pluginsWhat 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.00010 | $0.00916 |
| Opus 5 | $0.00005 | $0.00458 |
| Sonnet 5 | $0.00002 | $0.00183 |
| Haiku 4.5 | $0.00001 | $0.00092 |
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 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status Command
You are reporting on the current progress of the development tasks.
Input
- Argument: {{1}}
- (empty) - Show summary status
detailed- Show detailed status with task descriptions
Process
Step 1: Load Task Data
- Read the
tasks/00-index.mdfile - Read all individual task files (
tasks/XX-*.md) - Parse the YAML frontmatter from each task to get current status
If no tasks/ directory exists:
"No task breakdown found. Run
/software-engineer:plan <feature description>to create a development plan."
Step 2: Calculate Progress
Compute the following metrics:
- Total tasks: Count of all task files (excluding 00-index.md)
- Completed: Tasks with
status: done - In Progress: Tasks with
status: progress - Todo: Tasks with
status: todo - Progress percentage: (Completed / Total) × 100
Step 3: Display Status
Summary View (default)
📊 Development Progress
═══════════════════════════════════════════════════════
Progress: [████████████░░░░░░░░] 60% (12/20 tasks)
✅ Completed: 12 tasks
🔄 In Progress: 2 tasks
📋 Todo: 6 tasks
───────────────────────────────────────────────────────
Current Focus:
→ Task 13: [Task Title] (progress)
→ Task 14: [Task Title] (progress)
Next Up:
→ Task 15: [Task Title] (Priority: High)
→ Task 16: [Task Title] (Priority: Medium)
───────────────────────────────────────────────────────
Phase Progress:
Phase 1: Foundation ████████████████████ 100% ✓
Phase 2: Core ████████████████░░░░ 80%
Phase 3: Advanced ░░░░░░░░░░░░░░░░░░░░ 0%
Phase 4: Testing ████████░░░░░░░░░░░░ 40%
═══════════════════════════════════════════════════════
Detailed View (with detailed argument)
Include all the above, plus:
───────────────────────────────────────────────────────
📋 All Tasks
───────────────────────────────────────────────────────
Phase 1: Foundation
✅ 01. Project Setup (done) - Low complexity
✅ 02. Config Constants (done) - Low complexity
✅ 03. Exception Classes (done) - Low complexity
Phase 2: Core Implementation
✅ 04. Buffer Manager (done) - Medium complexity
🔄 05. Lexer/Tokenizer (progress) - High complexity
↳ Dependencies: Tasks 03, 04 ✓
↳ Acceptance: 3/5 criteria met
📋 06. Streaming Parser (todo) - High complexity
↳ Dependencies: Tasks 02, 03, 05 (waiting on 05)
[... continue for all tasks ...]
───────────────────────────────────────────────────────
🚧 Blockers & Issues
───────────────────────────────────────────────────────
• Task 05 is blocking tasks 06, 07, 08
• No critical issues reported
───────────────────────────────────────────────────────
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 · 123 lines · 10 tokens per session scan A 4078cf5aaed6
status is a command published in the GitHub repository FunkyOz/funkyoz-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 10 tokens to every session and 916 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-31.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.