Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/build-with-dhiraj/ai-workflow-framework-portability-kitnpx agentmods add skills/build-with-dhiraj/ai-workflow-framework-portability-kit/jove-labs-sweepWrote 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/build-with-dhiraj/ai-workflow-framework-portability-kit/jove-labs-sweep)<a href="https://agentmods.dev/skills/build-with-dhiraj/ai-workflow-framework-portability-kit/jove-labs-sweep"><img src="https://agentmods.dev/badge/skills/build-with-dhiraj/ai-workflow-framework-portability-kit/jove-labs-sweep/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/build-with-dhiraj/ai-workflow-framework-portability-kit/jove-labs-sweep"><img src="https://agentmods.dev/badge/skills/build-with-dhiraj/ai-workflow-framework-portability-kit/jove-labs-sweep.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.00211 | $0.18351 |
| Opus 5.5 | $0.00084 | $0.07340 |
| Sonnet 5.5 | $0.00042 | $0.03670 |
| Haiku 4.5 | $0.00021 | $0.01835 |
Grade B, and why
jove-labs-sweep scanned grade B with 1 finding 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 21d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
The reindex hook lives in `~/dev/jove-hq/.claude/settings.json`, so it only loads when the session is rooted at `jove-hq`. This skill is explicitly invocable from any cwd, and most runs happen from `~/dev`, where that fi How it starts
The opening of the file, as written. The whole thing — 707 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project root: every relative path in this skill (
knowledge/...,tools/...,.claude/skills/...) resolves against~/dev/jove-hq, never the current working directory. This skill is invocable from any cwd, so prefix accordingly:~/dev/jove-hq/knowledge/jove-labs/STATUS.md.
JoVE Labs sweep (the project-brain rebuild)
Purpose: Dhiraj should never have to tell Claude what happened on JoVE Labs. It was all recorded. This skill reconstructs the full picture from every surface into one canonical brief (knowledge/jove-labs/STATUS.md) so any session reads that instead of being fed context.
This is not the belt's daily sweep. The belt routines (08:06 jove-open-work-sync, 19:09 jove-ppp-eod-draft) are scheduled, delta-based, and all-work. This one is project-scoped, on-demand, deep, and its job is cross-source reconciliation plus doc hygiene. Read ownership per surface is in the precedence table in _shared/jove-connectors.md.
What changed in v2 (8 Aug 2026). Surfaces are data, not prose: they live in knowledge/jove-labs/surfaces.yaml. State lives in the repo at knowledge/jove-labs/.sweep/, not in the home directory, so both Claude config dirs converge on it. Coverage is asserted arithmetically instead of narrated. A run now says out loud whether it is converged with the other account.
/jove-labs-sweep means every surface, always (Dhiraj, 13 Aug 2026)
Standing instruction, and it overrides the group-scoping section below. When Dhiraj
invokes this skill by name, the run covers all five groups and every enabled surface in
surfaces.yaml. There is no such thing as a partial run by choice any more. Scoping to
one group is allowed only when he names the group in the same breath.
If it does not fit in one context, that is not a reason to cover less. It is the reason
to use the Workflow tool. He gave standing authorization for it here, in his own words:
"if this require batches then start a workflow to have the sweep run end to end of all
surfaces." That opt-in is scoped to this skill, and it does not generalise to other work.
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.
- 21d ago Changed · +21 lines · -1 tokens per session 0d49b3c2ea29
- 1mo ago First seen · 686 lines · 212 tokens per session scan B b18fd61b5c13
jove-labs-sweep is a skill published in the GitHub repository build-with-dhiraj/ai-workflow-framework-portability-kit (5 stars, last pushed 21d ago), licensed MIT. It adds 211 tokens to every session and 18,351 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-21.
Other skills, from other repositories
beads
Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or…
agents-md-improver
Audit and improve project-rules files (AGENTS.md, CLAUDE.md, .agents/instructions, local overrides) so the agent keeps accurate project context. Use when the user asks to check, audit, review, update, improve, or fix their AGENTS.md or CLAUDE.md, mentions "project rules maintenance" or "agent context optimization", or…
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…
agents-md-revise
Capture learnings from the current session into the project-rules file (AGENTS.md, CLAUDE.md, or local override) so future sessions benefit. Use when the user says "revise the rules", "update AGENTS.md / CLAUDE.md with what we just learned", "save this to project memory", "remember this for next time", or at the end…
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
session-handoff
Use when a working session is ending, the context window is nearly full, work needs to pass to a teammate or a fresh session, or the user says "hand this off", "write this up before we lose it", "I'm starting a new session", or "summarize where we are". Produces a handoff document that lets the next session resume…