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/vilnacrm-org/php-service-template/documentation-syncnpx skills add VilnaCRM-Org/php-service-template --skill documentation-syncgit clone --depth 1 https://github.com/VilnaCRM-Org/php-service-templateWhat 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 | $0.00015 | $0.00238 |
| Opus 5 | $0.00008 | $0.00119 |
| Sonnet 5 | $0.00003 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
documentation-sync 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 3d 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.
What it actually says
Documentation Sync
Documentation Surfaces In This Template
README.mdCONTRIBUTING.mdSECURITY.mdAGENTS.mdCLAUDE.md.github/openapi-spec/spec.yaml.github/graphql-spec/specworkspace.dsl
Update This Material When
- local commands change
- workflow or contributor expectations change
- API surfaces change
- architecture changes
- new agent-support files or conventions are added
Typical Sync Patterns
Makefile or workflow change
- update
README.md - update contributor guidance if review expectations changed
API change
- regenerate OpenAPI and GraphQL snapshots
- update
README.mdif user-visible commands or examples changed
Architecture change
- update
workspace.dsl - update
README.mdif the template structure guidance changed
Minimum Verification
- links and file references point to real paths
- command names match the current
Makefile - generated artifacts were refreshed in the same PR as the behavior change
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.
- 3d ago First seen · 49 lines · 15 tokens per session scan A 3f9ac36b97cc
documentation-sync is a skill published in the GitHub repository VilnaCRM-Org/php-service-template (24 stars, last pushed 2mo ago), licensed CC0-1.0. It adds 15 tokens to every session and 238 once invoked, about $0.0001 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…