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/yezannnnn/agentgroup/do_taskgit clone --depth 1 https://github.com/yezannnnn/agentGroupWhat 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.00829 |
| Opus 5 | $0.00000 | $0.00415 |
| Sonnet 5 | $0.00000 | $0.00166 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
do_task 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.
This is a copy
100% identical to do_task — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process Simone Task based on $Argument
IMPORTANT: Follow from Top to Bottom - don't skip anything!
CREATE A TODO LIST with exactly these 8 items
- Analyse scope from argument
- Identify task file
- Analyse the task
- Set status to in_progress
- Execute task work
- Placeholder
- Execute Code review
- Finalize Task status
1 · Analyse scope from argument
<$ARGUMENTS> ⇒ Task ID, Sprint ID, or empty (select next open task in current sprint).
2 · Identify task file
Search .simone/03_SPRINTS/ and .simone/04_GENERAL_TASKS/. If no open task matches, pause and ask the user how to proceed.
3 · Analyse the task
Read the task description. If anything is unclear, ask clarifying questions before continuing.
CRITICAL CONTEXT VALIDATION: Before executing any task spin up Parallel Subagents for these tasks:
- Sprint Context: Confirm task belongs to current sprint scope
- Dependencies: Check if any dependent tasks need to be completed first
- Requirements: Read relevant requirements docs in
.simone/02_REQUIREMENTS/ - Scope Verification: Ensure task aligns with current sprint objectives
IMPORTANT: If task references functionality from future sprints or has unmet dependencies, pause and ask for clarification.
4 · Set status to in_progress
- Find out the current local timestamp (YYYY-MM-DD HH:MM).
- Update front-matter to status: in_progress and set Updated time
- Update ./simone/00_PROJECT_MANIFEST.md to set task in progress, updated time and current Sprint Status.
5 · Execute task work
- Follow Description, Goal and Acceptance Criteria.
- Consult supporting docs in .simone/01_PROJECT_DOCS/ and .simone/02_REQUIREMENTS/.
- Iterate over subtasks:
- Pick the next incomplete subtask.
- Implement the required changes, consulting docs as needed.
- Mark the subtask done.
- Append a log entry to ## Output Log using the format
[YYYY-MM-DD HH:MM]: <message>. - Repeat until all subtasks are complete.
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 · 94 lines · 0 tokens per session scan A 56066c63ae30
do_task is a command published in the GitHub repository yezannnnn/agentGroup (149 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 829 tokens. A static security scan graded it A with 0 findings. It is 100% identical to do_task, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.