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 SII-Holos/synergy --skill development-standardsgit clone --depth 1 https://github.com/SII-Holos/synergyWrote 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/sii-holos/synergy/development-standards)<a href="https://agentmods.dev/skills/sii-holos/synergy/development-standards"><img src="https://agentmods.dev/badge/skills/sii-holos/synergy/development-standards.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.00071 | $0.01654 |
| Opus 5 | $0.00036 | $0.00827 |
| Sonnet 5 | $0.00014 | $0.00331 |
| Haiku 4.5 | $0.00007 | $0.00165 |
Grade A, and why
development-standards 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 7d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply Development Standards
Establish Ownership
- Read the nearest
AGENTS.mdand Development reference. - Trace the current implementation with
architecturewhen ownership crosses packages or domains. - Check whether the change needs a decision record: every non-trivial change MUST add or update an implemented record in
docs/decisions/in the same PR (mechanical/local edits exempt). Follow the path-encoded lifecycle/class scheme and format contract in Decision records; validate withbun run decision:check. - Load every focused workflow that applies:
- Web/shared product UI:
develop-frontend - LLM or internal-agent invocation:
integrate-llm - HTTP route, OpenAPI, SDK, or Web API client:
change-server-api - durable state, schema, index, or migration:
change-persistence - capabilities, permissions, control profiles, enforcement, or sandboxing:
change-execution-boundaries - Channel targets, providers, managed Projects, or Native Clarus:
change-channel-runtime - Browser ownership/control, Desktop native presentation, or WebRTC:
change-browser-runtime - plugin manifest, installation, runtime, bridge, marketplace, or UI host:
change-plugin-runtime - built-in agent, CLI command, or first-party tool:
add-agent,add-cli-command, oradd-tool - tests or manual runtime validation:
testing-guideanddevelop-synergy - Git/worktree/PR operations:
git-guide - broad simplification audits or decision-record coalescing:
find-simplifications
- Web/shared product UI:
- Use canonical product, architecture, reference, plugin, and operations documents for system truth. Keep Skills procedural; do not copy whole architecture descriptions into them.
Implement from Current Evidence
- Inspect schemas, tests, generated contracts, and at least one neighboring implementation before choosing a pattern.
- State the behavioral invariant and write the failing test first for new behavior or bug fixes.
- Change the smallest coherent set of owners. Include migrations, events, SDK generation, UI registration, or docs only when the contract crosses them.
- Run the narrowest verification first, then expand according to the affected workflow.
What ships with it
1 file 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.
- 7d ago First seen · 73 lines · 71 tokens per session scan A a83fb9e3fc5f
development-standards is a skill published in the GitHub repository SII-Holos/synergy (548 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 1,654 once invoked, about $0.0004 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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…