Borrowing it
Nothing to install: this file belongs to mussolene/1c_hbk_bsl. 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/mussolene/1c_hbk_bsl/main/AGENTS.mdgit clone --depth 1 https://github.com/mussolene/1c_hbk_bslWrote 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/mussolene/1c_hbk_bsl/agents-md)<a href="https://agentmods.dev/instructions/mussolene/1c_hbk_bsl/agents-md"><img src="https://agentmods.dev/badge/instructions/mussolene/1c_hbk_bsl/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/mussolene/1c_hbk_bsl/agents-md"><img src="https://agentmods.dev/badge/instructions/mussolene/1c_hbk_bsl/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.00616 | $0.00616 |
| Opus 5 | $0.00308 | $0.00308 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
1c_hbk_bsl 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 9d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OACS / ACS Repository Workflow
For substantial features, refactors, bug fixes, investigations, and release work, use OACS/ACS as the governed local context, evidence, and checkpoint layer. Do not create a parallel private task-artifact tree unless the user asks for one.
Required sequence:
- State task scope and explicit acceptance criteria (
AC1,AC2, ...). - Build or inspect repository context through OACS:
acs context build --intent repo_development --scope project --json. - Run external tools normally. OACS does not schedule tools; it records their canonical results as governed evidence.
- Treat command outputs, external retrieval, CI results, package publication,
deployment results, and manual verification as evidence:
acs tool ingest-result .... - Inspect important evidence with
acs evidence inspect <ev_...> --json. - If evidence should become durable project knowledge, distill it into memory and attach the evidence ref with the memory lifecycle commands.
- Record a checkpoint for each completed iteration with outcome, evidence
refs, and next step:
acs checkpoint add ... --evidence <ev_...> --json. - Run current verification and a leak/secret check before claiming completion.
Hard rules:
- Do not claim completion unless every acceptance criterion is
PASS. - Do not claim completion unless current verification, OACS evidence, and an OACS checkpoint exist for the iteration.
- Verifiers judge current files and current command results, not chat claims.
- OACS is not the tool orchestrator; it is the governed memory/context/evidence layer.
- Do not replace OACS context build with a local heuristic for substantial repository work.
- Standalone tool-result evidence does not enter
ContextCapsule.evidence_refsby itself. It is projected only through included memories that reference it. - Preserve attribution when distilling memory: user instructions, agent decisions, tool observations, project policies, human approvals, derived memory, and system policy are different roles.
- Do not read, print, or commit
.agent/oacs/key.json,.agent/oacs/unlocked.key,.agent/oacs,.oacs, local databases, passphrases, or private agent state.
See docs/oacs-development.md for repository-specific command examples.
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.
- 9d ago First seen · 58 lines · 616 tokens per session scan A f633bf668271
1c_hbk_bsl AGENTS.md is an instructions file published in the GitHub repository mussolene/1c_hbk_bsl (9 stars, last pushed 13d ago), licensed MIT. It adds 616 tokens to every session, about $0.0031 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-31.
Other instructions, from other repositories
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.
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).
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.