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 skills/devoxx/devoxxgenieideaplugin/start-tasknpx skills add devoxx/DevoxxGenieIDEAPlugin --skill start-taskgit clone --depth 1 https://github.com/devoxx/DevoxxGenieIDEAPluginWhat 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.00054 | $0.00789 |
| Opus 5 | $0.00027 | $0.00394 |
| Sonnet 5 | $0.00011 | $0.00158 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
start-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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start Task
Context
- Current branch: !
git branch --show-current - Working tree status: !
git status --short - Existing branches: !
git branch --list 'feature/task-*'
Your task
Create a feature branch for a backlog task and begin implementation.
The user will provide a task ID (e.g. task-123 or 123). If no task ID is provided, check the argument $ARGUMENTS for the task reference.
Step 1 — Load the task
- Normalize the input: if the user gave just a number like
123, treat it astask-123. - Use
mcp__backlog__task_viewto read the full task details: title, description, acceptance criteria, and any referenced files. - If the task is not found, use
mcp__backlog__task_searchto locate it. - Print a brief summary of the task for the user.
Step 2 — Ensure a clean working tree
- Check
git status. If there are uncommitted changes, warn the user and ask whether to stash them before proceeding. - Ensure we are on the main branch. If not, ask the user if they want to switch.
Step 3 — Create and switch to a feature branch
- Pull latest changes on main:
git pull --rebase. - Derive a branch name from the task:
feature/task-{id}-{slugified-title}(lowercase, hyphens, max ~60 chars).- Example: task 113 "Split app.css into native CSS modules" →
feature/task-113-split-css-modules
- Example: task 113 "Split app.css into native CSS modules" →
- Create and switch to the branch:
git checkout -b <branch-name>.
Step 4 — Mark the task as in-progress
- Use
mcp__backlog__task_editto set the task status toIn Progress.
Step 5 — Plan and implement
- Analyze the task description and acceptance criteria carefully.
- Read all files referenced in the task, plus any related code you need to understand.
- Create a plan and present it to the user for approval before writing code.
- Once approved, implement the changes following the project's patterns and conventions.
- After implementation, run the full verification suite:
npm run lint && npm run typecheck && npm test && npm run build:app && npx playwright test - Fix any issues found by the verification suite.
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 · 68 lines · 54 tokens per session scan A a4f080c4964f
start-task is a skill published in the GitHub repository devoxx/DevoxxGenieIDEAPlugin (677 stars, last pushed 5d ago), licensed MIT. It adds 54 tokens to every session and 789 once invoked, about $0.0003 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-30.
Other skills, from other repositories
agtx-sweep
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.
nap
Context hygiene — compress, prune, archive .squad/ state.
call-diagnostics
Analyze phone call observability data, detect problems, track them across calls, and recommend systematic repairs.
backlog
EXPERIMENTAL. Use when working the project-wide out-of-scope backlog at paad/code-reviews/backlog.md — cleaning it of entries that are already fixed or gone, or picking the next entry and fixing it end-to-end. Not for producing backlog entries — that is /agentic-review — and not for reviewing a branch diff.
backlog
Capture single backlog items, or list and triage an existing project backlog. Use this skill whenever the user wants to file a bug, feature request, or backlog item without writing a full PRD, including casual requests mid-conversation like "create an issue for that", "add this to the backlog", or "file a quick bug…
workflow-reference
This skill should be used when executing the epic-dev workflow, creating epic branches, managing sprint phases, working with git worktrees for phased feature development, or when the user mentions "epic dev", "epic-dev", "/epic-dev", "epic workflow", "sprint phases", "phased development", or "git worktree workflow".