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/create_general_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.01246 |
| Opus 5 | $0.00000 | $0.00623 |
| Sonnet 5 | $0.00000 | $0.00249 |
| Haiku 4.5 | $0.00000 | $0.00125 |
Grade A, and why
create_general_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 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.
This is a copy
100% identical to create_general_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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create General Task - Execute top to bottom
Creates a new general task in .simone/04_GENERAL_TASKS/ following project documentation standards.
Create a TODO with EXACTLY these 10 Items
- Parse task arguments and determine task ID
- Load project context and documentation requirements
- Verify task doesn't duplicate existing work
- Research codebase for implementation context
- Create task file using standard template
- Fill in task details with proper context
- Add technical guidance and codebase references
- Update project manifest with new task
- Validate task alignment with architecture
- Perform final quality check and report
DETAILS on every TODO item
1. Parse task arguments and determine task ID
The argument format is: <Task Title or Description>
- If arguments are empty, prompt user for task details
- Generate sequential task ID by examining existing tasks in
.simone/04_GENERAL_TASKS/ - Find highest task number (T###) and increment by 1
- Format:
T###_<Task_Title_Snake_Case>.md - IMPORTANT: Task IDs must be sequential with no gaps
2. Load project context and documentation requirements
Use PARALLEL SUBAGENTS to READ and UNDERSTAND the project's context:
- READ
.simone/00_PROJECT_MANIFEST.md- Get current project state and direction - READ
.simone/01_PROJECT_DOCS/ARCHITECTURE.md- Understand system constraints - READ latest files in
.simone/10_STATE_OF_PROJECT/- Review current state - SCAN
.simone/05_ARCHITECTURE_DECISIONS/for relevant ADRs - IMPORTANT: General tasks must align with documented architecture
3. Verify task doesn't duplicate existing work
SEARCH comprehensively for potential duplicates:
- Check all files in
.simone/04_GENERAL_TASKS/ - Search sprint tasks in
.simone/03_SPRINTS/*/T*.md - Look for similar functionality in completed milestones
- CRITICAL: If duplicate found, stop and report to user with file reference
4. Research codebase for implementation context
Based on the task description, use PARALLEL SUBAGENTS to:
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 · 147 lines · 0 tokens per session scan A 470f6acce061
create_general_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 1,246 tokens. A static security scan graded it A with 0 findings. It is 100% identical to create_general_task, differing in 0 lines, and is treated as a copy.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.