Borrowing it
Nothing to install: this file belongs to simke9445/agentlocks. 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/simke9445/agentlocks/main/AGENTS.mdgit clone --depth 1 https://github.com/simke9445/agentlocksWrote 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/simke9445/agentlocks/agents-md)<a href="https://agentmods.dev/instructions/simke9445/agentlocks/agents-md"><img src="https://agentmods.dev/badge/instructions/simke9445/agentlocks/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/simke9445/agentlocks/agents-md"><img src="https://agentmods.dev/badge/instructions/simke9445/agentlocks/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.01031 | $0.01031 |
| Opus 5.5 | $0.00412 | $0.00412 |
| Sonnet 5.5 | $0.00206 | $0.00206 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
agentlocks 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 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository instructions for agents
Agentlocks is a standalone advisory locking CLI (Bun/TypeScript dev stack, shipped as one Node bundle — a CLI, not a library). Keep defaults generic: do not add prompt-optimization behavior, command aliases, or repository-specific defaults.
Product maturity policy
Agentlocks is not live yet. Do not add compatibility layers, migration paths, deprecated aliases, or fallback behavior for previous internal layouts, schemas, CLI flags, actor outputs, or report formats. When a contract changes, update the implementation, tests, docs, skill instructions, and wiki in place to the new contract.
Commit policy
Make a commit every time a chunk of logic is implemented and unit tested. Do this whether you are working on a branch or inside a worktree: each passing unit-tested chunk gets its own commit before moving on to the next.
Branch and merge policy
Prefer trunk-based development: commit straight to main. agentlocks exists so multiple agents can
share one worktree without clobbering, so branching for isolation is usually unnecessary. Coordinate
with file locks, run bun run check before each commit, and push small green commits to main (see
Commit policy). No branch means no merge, so no history is ever collapsed or lost.
Branch only when a change must be gated before it reaches main (risky or large work needing CI or
review first), is a throwaway experiment, or comes from an outside contributor.
When you do merge a branch, preserve every commit. Never squash.
git merge --no-ff <branch>keeps every commit and the branch topology. Simplest, always safe.- Or rebase the branch onto
mainand fast-forward for a linear history that still keeps every commit; use this only when each branch commit is green. - Keep
mainbisect-safe: every commit, branch or not, must build and pass on its own (the Commit policy guarantees this, which is what makes preserving all commits safe). - Durable narrative (decisions, rejected approaches, lessons) lives in
CHANGELOG.mdand the task ledger, not commit history. - Delete the branch after merge; its commits already live on
main.
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 · 100 lines · 1,031 tokens per session scan A 1b43cdca5dbb
agentlocks AGENTS.md is an instructions file published in the GitHub repository simke9445/agentlocks (11 stars, last pushed 1mo ago), licensed MIT. It adds 1,031 tokens to every session, about $0.0041 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-30.
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).
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.