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 skills add infohata/mind-vault --skill ingest-backloggit 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/ingest-backlog)<a href="https://agentmods.dev/skills/infohata/mind-vault/ingest-backlog"><img src="https://agentmods.dev/badge/skills/infohata/mind-vault/ingest-backlog/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/infohata/mind-vault/ingest-backlog"><img src="https://agentmods.dev/badge/skills/infohata/mind-vault/ingest-backlog.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.00098 | $0.03477 |
| Opus 5 | $0.00049 | $0.01739 |
| Sonnet 5 | $0.00020 | $0.00695 |
| Haiku 4.5 | $0.00010 | $0.00348 |
Grade A, and why
ingest-backlog 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 5d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ingest-backlog
One-time bootstrap helper. A brownfield project that already has a monolithic idea/backlog markdown document cannot cleanly adopt the sprint workflow's per-idea convention until every entry has its own file. This skill does that migration mechanically: scan the legacy document, emit one file per entry, regenerate a lightweight index, and leave completed entries as footer lines (forward-only policy).
This is not part of the sprint loop. Run it once per brownfield project, review the diff, commit.
When to use
TRIGGER when:
- user says "ingest the backlog", "split IDEAS.md", "atomise the idea list", "convert BACKLOG.md into per-idea files", "bootstrap docs/ideas/"
- a project adopting the sprint workflow has a legacy monolithic backlog file and no existing
docs/ideas/tree /idearefuses to create because it detected a legacy file — this skill is the routed follow-up
SKIP when:
docs/ideas/already has files AND a legacy monolithic file also exists — mixed state. Abort and ask the user which source of truth wins before touching either.- the legacy file is under 100 lines with fewer than ~5 entries — just ask the user to split it by hand; the skill is over-engineered for that.
- the user wants to capture a new idea — route to
/idea. - the user wants to plan an existing idea — route to
/plan.
Pattern
1. Locate the source file
Scan in this order; stop at the first hit. Ask the user for an explicit path if multiple candidates exist or nothing is found.
Search paths (relative to project root):
IDEAS.md,BACKLOG.md,ROADMAP.md,TODO.md,FEATURES.mddocs/IDEAS.md,docs/BACKLOG.md, ...docs/execution/IDEAS.md,docs/execution/BACKLOG.md, ...docs/planning/IDEAS.md,docs/planning/BACKLOG.md, ...
If the user supplies an explicit path, honour it regardless of filename. The skill is agnostic about where the source lives.
2. Detect the format
Parse the source, identifying one of the recognised shapes in references/legacy-formats.md. The canonical shape uses H4 entries:
What ships with it
2 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.
- 5d ago Changed 8397b17e81d3
- 9d ago First seen · 205 lines · 98 tokens per session scan A 2d60cb00c3a7
ingest-backlog is a skill published in the GitHub repository infohata/mind-vault (2 stars, last pushed today), licensed Apache-2.0. It adds 98 tokens to every session and 3,477 once invoked, about $0.0005 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.