Borrowing it
Nothing to install: this file belongs to hiromaily/docs-ssot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hiromaily/docs-ssot/main/.github/instructions/docs.instructions.mdgit clone --depth 1 https://github.com/hiromaily/docs-ssotWrote 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/instructions/hiromaily/docs-ssot/docs)<a href="https://agentmods.dev/instructions/hiromaily/docs-ssot/docs"><img src="https://agentmods.dev/badge/instructions/hiromaily/docs-ssot/docs/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/instructions/hiromaily/docs-ssot/docs"><img src="https://agentmods.dev/badge/instructions/hiromaily/docs-ssot/docs.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.01292 | $0.01292 |
| Opus 5.5 | $0.00517 | $0.00517 |
| Sonnet 5.5 | $0.00258 | $0.00258 |
| Haiku 4.5 | $0.00129 | $0.00129 |
Grade A, and why
docs-ssot docs.instructions.md 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 1mo 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Rules for docs-ssot
SSOT Principle: Only Edit Source Files
This project generates documentation from source files. The pipeline is:
template/docs/**/*.md + template/*.tpl.md + docsgen.yaml
↓
docs-ssot build (make docs)
↓
README.md / AGENTS.md / CLAUDE.md
Generated Files — Never Edit Directly
The following are build artifacts and must NOT be modified:
README.mdAGENTS.mdCLAUDE.md
If you need to change content in these files, find the source file under docs/ that contains that section and edit it there, then run make docs.
Source Files — Where to Make Changes
All documentation content lives under docs/. Edit files here:
| Directory | Purpose |
|---|---|
docs/01_project/ |
Project overview, vision, background |
docs/02_product/ |
Product concept and feature descriptions |
docs/03_architecture/ |
System architecture, pipeline, diagrams |
docs/04_development/ |
Setup, testing, linting guides |
docs/05_ai/ |
AI tool-specific instructions (Claude, Cursor, Codex, etc.) |
docs/06_reference/ |
Commands reference, directory structure |
Templates — Structure Only
Template files in template/ define document structure using include directives. Modify templates only to change document structure (add/remove/reorder sections), not content.
template/README.tpl.md
template/AGENTS.tpl.md
template/CLAUDE.tpl.md
Adding New Content
- Create or edit the appropriate file under
docs/. - If it's a new file, add an include directive in the relevant
template/*.tpl.md:<!-- @include: docs/XX_category/new-file.md --> - Run
make docsto regenerate output files. - Commit both the source file and regenerated outputs together.
Include Directive Format
Include directives follow the VitePress style:
<!-- @include: path/to/file.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.
- 1mo ago First seen · 172 lines · 1,292 tokens per session scan A bae2913ac275
docs-ssot docs.instructions.md is an instructions file published in the GitHub repository hiromaily/docs-ssot (2 stars, last pushed 6mo ago), licensed MIT. It adds 1,292 tokens to every session, about $0.0052 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-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.