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/CLAUDE.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/claude-md)<a href="https://agentmods.dev/instructions/hiromaily/docs-ssot/claude-md"><img src="https://agentmods.dev/badge/instructions/hiromaily/docs-ssot/claude-md.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.14568 | $0.14568 |
| Opus 5 | $0.07284 | $0.07284 |
| Sonnet 5 | $0.02914 | $0.02914 |
| Haiku 4.5 | $0.01457 | $0.01457 |
Grade B, and why
docs-ssot CLAUDE.md scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
| Settings | `~/.claude/settings.json` | User-level global settings | How it starts
The opening of the file, as written. The whole thing — 2,039 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context
Overview
docs-ssot is a documentation Single Source of Truth (SSOT) generator.
It composes files such as README.md, CLAUDE.md, AGENTS.md, and other AI agent instruction files from small modular Markdown files.
Background
AI-assisted development and AI agents are becoming a standard part of software development workflows. Different AI tools and agents require different instruction and context files, for example:
- README.md
- AGENTS.md
- CLAUDE.md
- Agent-specific rule files like
.claude/rules,.cursor/rules - Development guidelines
- Architecture documentation
As the number of AI tools increases (Claude, Codex, Cursor, etc.), maintaining these files becomes difficult.
Common problems include:
- Documentation duplication
- Inconsistent information across files
- Outdated documentation
- Manual copy & paste maintenance
- Documentation drift over time
Maintaining multiple documentation files without duplication becomes increasingly difficult.
Problem
Documentation should follow the Single Source of Truth (SSOT) principle, but Markdown alone has limited reuse and composition capabilities.
Markdown is easy to write but lacks:
- File composition
- Reusable documentation modules
- Document templating
- Shared sections across multiple documents
- Structured documentation assembly
As a result, teams often duplicate content across multiple Markdown files.
Solution
docs-ssot solves this problem by introducing:
- Modular Markdown documentation
- Template-based document structure
- Include directives for Markdown files
- Generated documentation files
- Single Source of Truth documentation architecture
Instead of writing large README files directly, documentation is split into small reusable Markdown modules and assembled into final documents using templates.
Concept
Instead of maintaining large README files, this project splits documents into small reusable markdown modules and composes them into final documents.
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 · 2,039 lines · 14,568 tokens per session scan B 3f6b6ca87f42
docs-ssot CLAUDE.md is an instructions file published in the GitHub repository hiromaily/docs-ssot (2 stars, last pushed 4mo ago), licensed MIT. It adds 14,568 tokens to every session, about $0.0728 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.