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 sorah/config --skill spec-conventionsgit clone --depth 1 https://github.com/sorah/configWrote 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/sorah/config/spec-conventions)<a href="https://agentmods.dev/skills/sorah/config/spec-conventions"><img src="https://agentmods.dev/badge/skills/sorah/config/spec-conventions/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/sorah/config/spec-conventions"><img src="https://agentmods.dev/badge/skills/sorah/config/spec-conventions.svg" alt="Reviewed on agentmods" width="80" 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.00065 | $0.00940 |
| Opus 5.5 | $0.00026 | $0.00376 |
| Sonnet 5.5 | $0.00013 | $0.00188 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
spec-conventions 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 yesterday.
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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec File Conventions
Conventions for writing implementation-ready specification documents that serve as the single source of truth for feature design and implementation.
Spec Files vs Documentation Files
Projects often maintain two distinct documentation layers. Understand the distinction to keep each layer focused.
Spec Files
- Purpose: Single source of truth for design and implementation decisions
- Audience: Implementors and reviewers
- Content: Full design details — schemas, field definitions, decision rationale, implementation notes
- Lifecycle: Created before implementation, updated progressively during implementation
- Self-contained: A reader should understand the full design without opening other files
Documentation Files
- Purpose: Quick-reference guides after implementation
- Audience: Developers using the feature
- Content: Usage-focused ("how to use"), not "how it was designed"
- Brevity: Avoid duplicating definitions — point to source files (.sql, .proto, .rb, config files)
- No historical context: Omit decision rationale and alternatives considered
When a spec lists documentation files as deliverables, verify their scope is clear. The spec itself must contain enough inline detail to be self-contained — never defer design details to documentation files.
Spec File Structure
A well-structured spec includes:
- Title and overview — what the feature does and why it's needed
- Data model — include full DDL or schema definitions, not just prose descriptions
- Architecture — name concrete classes/modules; specify where each piece of logic lives
- Behavior — cover the happy path end-to-end, then every error condition and edge case
- Integration — specify which existing modules are touched and how
- Security considerations — credential handling, rate limiting, audit logging, sensitive data
- Operations — setup steps, cleanup/purge strategies, key rotation procedures
- Scope — explicitly state what's in and out; note dependencies on future work
- Deliverables — enumerate every file to create or modify
- Current Status — interview or implementation progress (see below)
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.
- yesterday First seen · 117 lines · 65 tokens per session scan A d8421e63f8db
spec-conventions is a skill published in the GitHub repository sorah/config (31 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 940 once invoked, about $0.0003 per session on Opus 5.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-10-17.
Other skills, from other repositories
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…
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.