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 quanghoangf/vibedoc --skill nextgit clone --depth 1 https://github.com/quanghoangf/vibedocWrote 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/quanghoangf/vibedoc/next)<a href="https://agentmods.dev/skills/quanghoangf/vibedoc/next"><img src="https://agentmods.dev/badge/skills/quanghoangf/vibedoc/next/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/quanghoangf/vibedoc/next"><img src="https://agentmods.dev/badge/skills/quanghoangf/vibedoc/next.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.00173 | $0.01443 |
| Opus 5.5 | $0.00069 | $0.00577 |
| Sonnet 5.5 | $0.00035 | $0.00289 |
| Haiku 4.5 | $0.00017 | $0.00144 |
Grade A, and why
next 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 14d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What next
Answer "what should I do now?" with one recommendation and a command the user can run immediately. A list of ten options is not an answer. The user asked because they didn't want to weigh options themselves. Do the weighing, show the reasoning in a line or two, and keep the alternatives short.
This skill only reads. Don't change task or roadmap files, and don't start the recommended work until the user says so.
1. Gather the state
Read these, in any order. Prefer the VibeDoc MCP tools when they're connected (vibedoc_get_status, vibedoc_get_roadmap, vibedoc_list_tasks). Otherwise read the files directly. Either way it's cheap, so read everything below before deciding.
- Tasks:
plans/tasks/T*.md. For each: id, title, status,Depends on, andDuefrom the**Key:** Valueblock under the H1, plus any## Verificationfindings (critical / major / minor). - Roadmap:
plans/roadmap/R*.md. Items with no**Parent:**are horizons, and items with one are epics. For each epic: status,**Tasks:**list, andDue.vibedoc_get_roadmapalso lists "Needs attention" (status drift, overdue, at risk, unmerged spec changes, conflicting spec changes, uncovered scenarios). - Activity:
.vibedoc-activity.json. You need the lasttask_updatedtime for each in-progress task, to tell active work from abandoned work. - Handoff: the "Handoff for next session" / "Up next" part of
memory/MEMORY.md, if it exists. It is the last session's intent. Weigh it, but check it against the files, because it goes stale. - Git: current branch, uncommitted changes, and commits not pushed yet (
git status -sb,git log @{u}..when there is an upstream).
2. Pick the first rule that applies
The order runs from "something is stuck or at risk" to "start something new". Unblocking beats starting, because a stuck task holds up everything that depends on it, and starting new work on top of a mess makes the mess bigger.
| # | Situation | Recommend |
|---|---|---|
| 1 | Uncommitted changes, or a branch with unpushed commits, that look like finished work | Commit or push / open a PR (/commit, /create-pr). Say what the changes are. |
| 2 | A task is blocked, or an epic's queue would report "Needs a human" (blocked task, missing task file, broken dependency) |
Unblock it: read its ## Blocked because note if there is one and say what decision is needed. |
| 2b | A task in review or done has critical or major findings in its ## Verification (the card shows "N findings"), and they aren't outdated |
Send them back from the task panel (tick the findings → Send back N findings), or say which finding is wrong if you disagree. Name the task and the findings. |
| 3 | A task is in-progress with no activity for more than ~24h |
It's probably abandoned: resume it, or move it back to todo so the queue can hand it out again. |
| 4 | An epic has ready tasks: todo, with every dependency done or cancelled |
/vibedoc:work <epic>. Prefer an epic that is already in-progress, then the earliest horizon, then by Order. Name the task it would start with. |
| 5 | Roadmap drift: all of an epic's tasks are done but the epic isn't, an epic is planned while its tasks are moving, or something is overdue |
Fix the status or due date (vibedoc_update_roadmap_item, or edit the **Status:** line). |
| 5b | Spec drift under "Needs attention" in vibedoc_get_roadmap: a done epic whose spec changes aren't merged, two open epics changing the same requirement, or a scenario no task covers |
Unmerged: Merge into capability spec on the epic's sheet (a person does it). Conflict: decide which epic owns the requirement and edit the other's ## Spec changes. Uncovered scenario: add **Covers:** to a task, or a task for it, before work starts. |
| 6 | The earliest horizon has a planned epic with no tasks | /vibedoc:breakdown <epic>. Pick the first one by horizon order, then by Order. |
| 7 | No roadmap at all (plans/roadmap/ empty or missing) |
/vibedoc:roadmap. |
| 8 | Nothing above applies | Say the project is in a clean state, and suggest /vibedoc:roadmap to plan the next horizon. |
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.
- 14d ago First seen · 55 lines · 173 tokens per session scan A 555b2a73c2f6
next is a skill published in the GitHub repository quanghoangf/vibedoc (7 stars, last pushed 4d ago), licensed MIT. It adds 173 tokens to every session and 1,443 once invoked, about $0.0007 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-10-06.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.