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 sync-ref-wipgit 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/sync-ref-wip)<a href="https://agentmods.dev/skills/digital-stoic-org/agent-skills/sync-ref-wip"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/sync-ref-wip.svg" alt="Measured on agentmods" 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.00053 | $0.01429 |
| Opus 5 | $0.00026 | $0.00714 |
| Sonnet 5 | $0.00011 | $0.00286 |
| Haiku 4.5 | $0.00005 | $0.00143 |
Grade A, and why
sync-ref-wip 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 8d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync ref ↔ wip
Bidirectional alignment between ref (stable reference) and wip (working documents).
Folder aliases: ref folder may be named ref/ or reference/. Wip folder may be named wip/ or work-in-progress/. Detect from the paths provided — both are equivalent.
⚠️ AskUserQuestion Guard
After EVERY AskUserQuestion call, check if answers are empty/blank. If empty: output "⚠️ Questions didn't display (known bug).", present options as numbered text list, WAIT for user reply.
Phase 0: Resolve Files
If called by user ($ARGUMENTS is empty or auto):
- Glob for ref folder (
ref/orreference/) and wip folder (wip/orwork-in-progress/) in current directory - If neither found → abort: "⚠️ No ref/ or wip/ folder found. Use /switch to navigate to a project first."
- List files in both folders with last-modified dates
- Present menu:
🔄 Sync ref ↔ wip 🔒 ref/ files: 1. persona-claire-v2.md (Mar 16) 2. positioning-frameworks-v2.md (Mar 16) ✏️ wip/ files: 3. brand-instance.md (Mar 16) 4. content-marketing.md (Feb 27) Pick ref + wip file to sync (e.g. "1 3"), or "all" to scan everything: - If user picks specific pair → set
ref_fileandwip_file - If user picks "all" → scan all wip files for ref references, report drift for each pair found, ask which to fix
If called with arguments (two paths or by /save-work):
- Parse
ref_fileandwip_filefrom arguments drift_descriptionfrom context or "auto-detect"
Phase 1: Detect Direction
Read both files in parallel. Also check timestamps:
stat -c '%Y %y' {ref_file} {wip_file}
Direction heuristics (check in order, first match wins):
| Signal | Direction | Reasoning |
|---|---|---|
| ref is newer than wip + wip references old ref terms | ref → wip | ref was updated, wip hasn't caught up |
| wip is significantly newer + wip contains structured content absent from ref (versioned headers, decision tables, validated sections marked with dates) | wip → ref | wip has matured, ref is outdated |
| drift_description says "stale link" or "dead link" or "old terminology" | ref → wip | classic drift — wip points to outdated ref |
| drift_description says "promote" or "mature" or "validated" | wip → ref | explicit promotion request |
wip has [Proposition] markers removed + content reviewed (dates, signatures, version bumps in wip) |
wip → ref | wip graduated past draft stage |
| Cannot determine | ref → wip | safe default — ref is source of truth |
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.
- 8d ago First seen · 134 lines · 53 tokens per session scan A 7483f43d31e2
sync-ref-wip is a skill published in the GitHub repository digital-stoic-org/agent-skills (20 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 1,429 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…