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 digital-stoic-org/agent-skills --skill sweep-projectgit clone --depth 1 https://github.com/digital-stoic-org/agent-skillsWrote 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/digital-stoic-org/agent-skills/sweep-project)<a href="https://agentmods.dev/skills/digital-stoic-org/agent-skills/sweep-project"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/sweep-project/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/digital-stoic-org/agent-skills/sweep-project"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/sweep-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 5 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00066 | $0.02163 |
| Opus 5 | $0.00033 | $0.01081 |
| Sonnet 5 | $0.00013 | $0.00433 |
| Haiku 4.5 | $0.00007 | $0.00216 |
Grade A, and why
sweep-project 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 10d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sweep Project
Periodic cleanup + reorganization + consistency check for one project at a time. Three gated phases: 1) audit (read-only) → 2) plan → 3) execute. Human approves between each.
Covers everything in the project: technical artifacts, deliverables, context files (CONTEXT-*-llm.md),
indexes, manifests, raw inputs, and parking of what's no longer active.
References (read on demand, do NOT inline): references/operating-rules.md (⚠️ hard constraints + AskUserQuestion guard + output style — read first, every run) · references/convention.md (zones + tiers) · references/drift-rules.md (the 5 checks) · references/templates.md (report skeletons).
Auto-invoke: dual-invocable by design. Despite Phase 3 moving/editing files, the three gates (audit → plan → execute, each human-approved) make autonomous misfire safe — so it stays auto-invocable rather than disable-model-invocation.
Phase 0: Resolve Target & Convention
- Resolve project path from
$ARGUMENTS. If empty: glob forCLAUDE.mdunder$COWORK_ROOT/git rev-parse --show-toplevel/ cwd (max depth 3), list candidates, ask which one. One project only. - Read the project's
CLAUDE.md— extract its declared folder structure, mutability table, any tier ontology, and naming rules. This is the authoritative spec for this project. Where it's silent, fall back toreferences/convention.md. Note any file-listing inside CLAUDE.md — that inventory is Axis-0 drift (belongs in INDEX.md). - Detect zones + map roles: detect
in/ src/ ref/ wip/ park/+ satellites (sync/ converted/ .tmp/ .dump/). For semantic-folder projects (own folder names), map each folder to a canonical role perreferences/convention.md§Hybrid role-mapping — keep names, govern by role. Note missing/extra zones and the folder→role map. - Detect traceability artifacts:
INDEX.md,in/MANIFEST.md,wip/00-index.md,sync/**/_manifest.yaml, any project-localSWEEP.md. Note which are missing. - Determine which phase to run (
--phase, else start at audit).--phase plan/executerequire the prior artifact — look for the latestAUDIT-*/PLAN-*in<P>/.tmp/sweep-project/. If the needed artifact is missing (or--phase executehas no approved plan), say so and restart from the earliest phase that has its inputs; never execute moves/edits without an approved plan. Confirm the project + detected convention in one short line before proceeding.
What ships with it
4 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.
- 10d ago First seen · 92 lines · 66 tokens per session scan A 25ea2153238a
sweep-project is a skill published in the GitHub repository digital-stoic-org/agent-skills (20 stars, last pushed 3d ago), licensed MIT. It adds 66 tokens to every session and 2,163 once invoked, about $0.0003 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-30.
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.