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 agentmods add skills/darellchua2/opencode-config-template/documentation-sync-workflow-skillnpx skills add darellchua2/opencode-config-template --skill documentation-sync-workflow-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/documentation-sync-workflow-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/documentation-sync-workflow-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/documentation-sync-workflow-skill.svg" alt="Measured on agentmods" 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.00034 | $0.01761 |
| Opus 5 | $0.00017 | $0.00881 |
| Sonnet 5 | $0.00007 | $0.00352 |
| Haiku 4.5 | $0.00003 | $0.00176 |
Grade A, and why
documentation-sync-workflow-skill 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 2d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I ensure documentation files stay synchronized when adding new skills or subagents by guiding updates to 4 key files:
- setup.sh - Update skill/agent counts and listings
- setup.ps1 - Update skill/agent counts and listings
- README.md - Update tables reflecting current skills/agents
- AGENTS.md - Document workflow guidance for new additions
When to use me
Use this workflow when:
- Adding a new skill to the
skills/directory - Adding a new subagent to the
agents/directory - Removing or renaming skills/subagents
- Verifying documentation accuracy
Prerequisites
- Write access to repository files
- Knowledge of skill category (for new skills)
- Knowledge of subagent purpose and associated skills (for new subagents)
Files Requiring Updates
1. setup.sh
AGENTS Section: Search for AGENTS ( to find the agent listing.
Update when: Adding a new primary agent
SKILLS Section: Search for SKILLS ( to find the skill listing.
SKILLS (49):
Framework (7): test-generator-framework, linting-workflow,
...
Documentation (2): coverage-readme-workflow, docstring-generator
...
Update when: Adding a new skill - increment count and add to appropriate category
2. setup.ps1
SKILLS Section: Search for SKILLS ( (mirrors setup.sh).
Update when: Adding a new skill - same changes as setup.sh
3. README.md
Skill Categories Table: Search for | Category | Skills | to locate.
| Category | Skills | Purpose |
|-----------|---------|---------|
| **Framework** (7) | ... | Generic workflows, testing patterns |
| **Documentation** (2) | coverage-readme-workflow, docstring-generator | Documentation generation |
Update when: Adding a new skill - add to or update appropriate category row
Subagents Table: Search for | Subagent | Purpose | to locate.
Update when: Adding a new subagent - add row with purpose and associated skills
4. AGENTS.md
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.
- 2d ago First seen · 229 lines · 34 tokens per session scan A b1e04f0220bb
documentation-sync-workflow-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 5d ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,761 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
keep-the-why
Extract and preserve the reasoning code cannot explain - decisions, rejected alternatives, workarounds, incidents, constraints - plus project setup and maintainer interviews. Not for what changed (see Keep a Changelog) - only why.
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
review
Adversarial fresh-context review of an increment before it ships. Every finding cites path:line and is re-verified. Use when saying "review", "grill this", or "critique the implementation".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".
summarize
Summarize conversations, logs, docs, or investigation notes into action-oriented text with evidence tags. Use for recap, handoff, CI failure digest, or MEMORY. Triggers: 总结, 汇总, summarize, 交接, 复盘, 调试总结.
pre-modification-check
Use before modifying, refactoring, moving, or deleting files in a Repowise-indexed repository, especially shared utilities, core modules, public APIs, or files the user did not explicitly identify.