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.
git clone --depth 1 https://github.com/yezannnnn/agentGroupWrote 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/yezannnnn/agentgroup/create_general_task)<a href="https://agentmods.dev/commands/yezannnnn/agentgroup/create_general_task"><img src="https://agentmods.dev/badge/commands/yezannnnn/agentgroup/create_general_task/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/yezannnnn/agentgroup/create_general_task"><img src="https://agentmods.dev/badge/commands/yezannnnn/agentgroup/create_general_task.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01246 |
| Opus 5.5 | $0.00000 | $0.00498 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (150 stars, last pushed 5mo 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
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.