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/infohata/mind-vault/worknpx skills add infohata/mind-vault --skill workgit clone --depth 1 https://github.com/infohata/mind-vaultWrote 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/infohata/mind-vault/work)<a href="https://agentmods.dev/skills/infohata/mind-vault/work"><img src="https://agentmods.dev/badge/skills/infohata/mind-vault/work.svg" alt="Measured on agentmods" 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 | $0.00076 | $0.04815 |
| Opus 5 | $0.00038 | $0.02407 |
| Sonnet 5 | $0.00015 | $0.00963 |
| Haiku 4.5 | $0.00008 | $0.00481 |
Grade A, and why
work 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 4d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
work
Third stage of the five-stage sprint workflow (idea → brainstorm/plan → work → review → compound). Executes a plan against the target project's codebase — spawns worktrees when the plan flags parallelism, dispatches to implementation personas, commits feature-by-feature, and tracks progress against the plan's Execution Sequence.
This skill is intentionally thin. It does not re-decide anything the plan already decided. It orchestrates; the personas implement; the rules guardrail. If the plan is wrong, stop and route back to /plan — don't paper over planning gaps at execution time.
When to use
TRIGGER when:
- user says "work the plan", "execute the plan", "implement plan X", "start working on Y", "ship the plan at "
- a
/planinvocation just completed and the natural next step is execution - a plan file exists at
<project>/docs/archive/*-<slug>/*-<slug>-plan.mdwithstatus: readyand the user wants to proceed
SKIP when:
- there is no plan file and the work is bounded enough to not need one — just do the fix
- the plan is still
status: draft— route to/planto finalise (architect review, open-questions resolution) first - the plan has clear structural flaws (missing file paths, unresolved architect findings) — route back to
/plan - the user wants to review or critique existing code — route to
/<engine>-loop
Pattern
1. Load and validate the plan
- Resolve the plan path from the argument (explicit path, slug, or most recent plan file). Read the whole file.
- Check frontmatter:
status: readyrequired. Ifdraft, refuse and route to/planfor finalisation. - Read the plan's Execution Sequence — this is the ordered list of work items the skill will dispatch.
- Read the plan's Verification section — the skill will run these commands/checks after execution completes.
- If the plan lists dependencies (open questions, prerequisite merges), verify they're resolved before starting.
2. Branch and worktree setup
What ships with it
7 files 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.
- 4d ago First seen · 255 lines · 76 tokens per session scan A 20459fac995b
work is a skill published in the GitHub repository infohata/mind-vault (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 76 tokens to every session and 4,815 once invoked, about $0.0004 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-31.
Other skills, from other repositories
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
glab-issue
Create, view, update, and manage GitLab issues. Use when working with issue tracking, bug reports, feature requests, or task management. Operations include creating issues, listing with filters, viewing details, adding comments/notes, updating labels/assignees/milestones, closing/reopening, and board management.…
sales-ops
Set up and run Airtable-based sales operations and CRM workflows — pipeline management, account and renewal management, deal desk, RFP / tender pipelines, partner CRMs, sales forecasting, vertical CRMs (real estate, mortgage, brokerage, capital markets, public works, nonprofit), and AI-native lean stacks…
jira
Search and manage Jira issues using JQL queries, create/update tickets, and manage workflows. Use when asked to find Jira tickets, check the backlog, manage sprints, track bugs, or work with Atlassian project management.
github
Use this skill when Enoch needs to coordinate work with GitHub: branches, pull requests, issues, reviews, comments, checks, and merges.