Borrowing it
Nothing to install: this file belongs to SoundBlaster/XcodeMCPWrapper. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SoundBlaster/XcodeMCPWrapper/main/.agents/skills/workplan-task-ops/SKILL.mdgit clone --depth 1 https://github.com/SoundBlaster/XcodeMCPWrapperWrote 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/skills/soundblaster/xcodemcpwrapper/workplan-task-ops)<a href="https://agentmods.dev/skills/soundblaster/xcodemcpwrapper/workplan-task-ops"><img src="https://agentmods.dev/badge/skills/soundblaster/xcodemcpwrapper/workplan-task-ops/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/skills/soundblaster/xcodemcpwrapper/workplan-task-ops"><img src="https://agentmods.dev/badge/skills/soundblaster/xcodemcpwrapper/workplan-task-ops.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.00053 | $0.00644 |
| Opus 5.5 | $0.00021 | $0.00258 |
| Sonnet 5.5 | $0.00011 | $0.00129 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
workplan-task-ops 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 2mo 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workplan Task Ops
Manage task lifecycle operations in SPECS/Workplan.md using the repository conventions.
Required Inputs
Collect these before running any operation:
- Target task ID (or task type and parent context if creating a new task)
- Target phase/backlog section in
SPECS/Workplan.md - Current status marker (
⬜️open or✅completed)
Use these sources of truth:
SPECS/TASK_TEMPLATE.mdfor task entry format and markersSPECS/Workplan.mdfor the actual task listscripts/pick_next_task.pyfor next-task selection and completion state updates
Operation 1: Add Task
- Determine task ID convention before editing:
- Phase task:
P{phase}-T{n} - Follow-up task:
FU-{parent/topic}-{n} - Bug task:
BUG-T{n}
-
Place the task in the correct section of
SPECS/Workplan.md. -
Copy the open-task block from
SPECS/TASK_TEMPLATE.mdand fill all fields:
- Header with
⬜️marker Description,Priority,Dependencies,ParallelizableOutputs/ArtifactsAcceptance Criteriawith unchecked boxes
- Validate task entry quality:
- ID is unique in workplan
- Dependencies reference existing tasks or
none - Acceptance criteria are testable
Operation 2: Pick Next Task
- Run:
python3 scripts/pick_next_task.py
-
Read the suggested task and dependency statuses.
-
Confirm the suggestion is still open in
SPECS/Workplan.md(⬜️) and not archived. -
Update
SPECS/INPROGRESS/next.mdusing the output template inSPECS/COMMANDS/SELECT.md.
Operation 3: Mark Task Completed
-
Confirm completion evidence exists (implementation done, validation/review state consistent).
-
Update the task block in
SPECS/Workplan.md:
- Change header marker from
⬜️to✅ - Add or update
Statusline with date when applicable - Check completed acceptance criteria (
[x])
- Persist completion for selector state:
python3 scripts/pick_next_task.py --done <TASK_ID>
- Verify follow-up selection:
python3 scripts/pick_next_task.py
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 80 lines · 53 tokens per session scan A 79edf7131ad4
workplan-task-ops is a skill published in the GitHub repository SoundBlaster/XcodeMCPWrapper (20 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 644 once invoked, about $0.0002 per session on Opus 5.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
omh-research-department
This is a Hermes-native research-department workflow skill.
omh-agent-board
This is a Hermes-native agent-board workflow skill.
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
bo-process-optimization
A method for examining a business workflow to find waiting, rework, handoff waste, and other delays, then proposing improvements and ways to measure them. It separates observed facts from possible explanations and suggestions.
bo-risk-assessment
A method for assessing operational risks in a process, project, or supplier arrangement using observed facts, possible consequences, and practical response suggestions. It keeps the likelihood of a consequence conditional unless the evidence supports more.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.