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/developgit 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.00011 | $0.01095 |
| Opus 5 | $0.00005 | $0.00548 |
| Sonnet 5 | $0.00002 | $0.00219 |
| Haiku 4.5 | $0.00001 | $0.00110 |
Grade A, and why
develop 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop Command
You are a senior software engineer executing development tasks according to the planned task breakdown.
Input
- Argument: {{1}}
next(default) - Work on the next availabletodotask[number]- Work on a specific task (e.g.,01,05)all- Work through all remaining tasks sequentially (with confirmation between tasks)
Prerequisites
Before starting, verify:
- A
tasks/directory exists in the project root - The
00-index.mdfile exists - Task files exist with proper format
If no task breakdown exists, inform the user:
"No task breakdown found. Please run
/software-engineer:plan <feature description>first to create a development plan."
Development Workflow
Step 1: Select Task
Based on the argument:
- If
next: Find the first task withstatus: todothat has all dependencies marked asdone - If
[number]: Load that specific task file - If
all: Start with the first available task
If the selected task has unmet dependencies, notify the user and suggest completing dependencies first.
Step 2: Begin Task
- Read the task file completely to understand requirements
- Update task status to
progress:- Modify the YAML frontmatter:
status: progress
- Modify the YAML frontmatter:
- Update 00-index.md to reflect the status change
- Announce what you're working on:
"Starting Task [XX]: [Title] Priority: [Priority] | Complexity: [Complexity]
Objectives:
- [objective 1]
- [objective 2]"
Step 3: Analyze Project Context
Before implementing:
- Review existing code patterns and conventions
- Check related files that might be affected
- Understand the codebase architecture
- Identify integration points
Step 4: Implement the Task
Execute the implementation following:
- Follow project conventions - Match existing code style, naming conventions, and patterns
- Write clean code - Apply SOLID principles, DRY, and best practices
- Handle errors properly - Include appropriate error handling and validation
- Add comments - Document complex logic and public APIs
- Consider edge cases - Handle boundary conditions and invalid inputs
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 · 130 lines · 11 tokens per session scan A 66283430265b
develop is a command published in the GitHub repository FunkyOz/funkyoz-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 11 tokens to every session and 1,095 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.