Borrowing it
Nothing to install: this file belongs to SenMuShare/senmu-buildos. 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/SenMuShare/senmu-buildos/main/AGENTS.mdgit clone --depth 1 https://github.com/SenMuShare/senmu-buildosWrote 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/senmushare/senmu-buildos/agents-md)<a href="https://agentmods.dev/instructions/senmushare/senmu-buildos/agents-md"><img src="https://agentmods.dev/badge/instructions/senmushare/senmu-buildos/agents-md/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/senmushare/senmu-buildos/agents-md"><img src="https://agentmods.dev/badge/instructions/senmushare/senmu-buildos/agents-md.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.00488 | $0.00488 |
| Opus 5.5 | $0.00195 | $0.00195 |
| Sonnet 5.5 | $0.00098 | $0.00098 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
senmu-buildos AGENTS.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 29d 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
Senmu BuildOS product source
This directory is the complete, distributable product source. It may be checked out alone or maintained as a declared subtree; use the actual Git root and source-relative path. Installed copies are execution artifacts, not a place to maintain source.
-
Establish the requested mode, goal, scope and observable completion; resolve consequential unknowns without re-asking settled choices. Start from the requested capability and its existing owner. Eight peer Skills live in
skills/; Hooks inhooks/; host adapters inadapters/. Usedocs/architecture/skill-boundaries.mdwhen ownership or routing is unclear, not as a universal pre-read. -
Preserve authorization, safety, truthful evidence and approved behavior. Reuse existing implementations and references; update affected consumers rather than duplicating complete rules. Runtime guidance and links remain portable.
-
Keep raw feedback, private tasks, credentials, user transcripts and author-only state outside this product. A public, synthetic regression or a useful architecture decision may remain here. Product checks and runtime cannot require a private sibling directory.
-
Use a scoped task branch and the project's actual write boundaries. Do not edit an installed cache or force-push unrelated work. A source commit does not authorize installation or public release.
-
Every completed product-change batch delivered as an update needs a new unified version, changelog and release notes; intermediate commits share one unpublished candidate. Explicit no-release instructions remain binding.
-
For each GitHub-bound change, assess all three READMEs and synchronize affected content; preserve unchanged sections and record the impact decision in the existing PR/task. Follow README maintenance; do not invent runtime changes or publication claims.
During development, select the affected existing test file with unittest discovery; add coverage only for a real gap. Full candidate checks (not after every edit):
python3 scripts/validate_package.py
python3 scripts/validate_public_surface.py
python3 scripts/bump_version.py --check
python3 -m unittest discover -s tests -p 'test_*.py'
node --test tests/hooks/*.test.js
Reuse valid source evidence across stages; keep artifact checks separate and stop when the required result is established. Preserve unverified limitations; passing source checks does not prove host activation or model performance. Contributor and release-source guidance is in CONTRIBUTING.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.
- 29d ago Changed · +1 lines · +87 tokens per session b9f2f15d680a
- 1mo ago Changed · +9 lines · +84 tokens per session 3a63321b9dc1
- 1mo ago Changed · +2 lines · +118 tokens per session 1d687a3b4364
- 1mo ago First seen · 12 lines · 199 tokens per session scan A f19a84846f85
senmu-buildos AGENTS.md is an instructions file published in the GitHub repository SenMuShare/senmu-buildos (2 stars, last pushed 20d ago), licensed Apache-2.0. It adds 488 tokens to every session, about $0.0020 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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.