Borrowing it
Nothing to install: this file belongs to sebastienrousseau/noyalib. 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/sebastienrousseau/noyalib/main/AGENTS.mdgit clone --depth 1 https://github.com/sebastienrousseau/noyalibWrote 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/sebastienrousseau/noyalib/agents-md)<a href="https://agentmods.dev/instructions/sebastienrousseau/noyalib/agents-md"><img src="https://agentmods.dev/badge/instructions/sebastienrousseau/noyalib/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/sebastienrousseau/noyalib/agents-md"><img src="https://agentmods.dev/badge/instructions/sebastienrousseau/noyalib/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.00485 | $0.00485 |
| Opus 5 | $0.00243 | $0.00243 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
noyalib 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 5d 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
Working on noyalib with an AI agent
The invariants a contribution must respect, whether typed by a human
or generated with an assistant. DEVELOPMENT.md covers the how;
this file covers the rules that are easy for an agent to violate.
Versioning and branches
- Releases increment strictly by +0.0.1, six crates in lockstep
at the identical
=0.0.X(ADR-0005). Never propose a 0.1.0 or 1.0 jump. - At most two version branches exist at once: the release in flight and one future branch. New work lands on the single future branch, sequenced by commits, never by more branches.
- Commit or stash everything (untracked files included) before any
branch switch, and never
git add -Aafter a switch without readinggit statusfirst.
Quality gates
- CI must be green in the same session that turned it red.
- Every behaviour change lands with its test in the same commit; a regression fix lands with the input that found it.
- Run the local battery before pushing:
cargo fmt --all -- --check, clippy, the affected test suites,reuse lint, codespell, markdownlint. Theverify-release-versions.shgate is the authority on version-bearing files. - A parse-behaviour change is a breaking change even when no
Rust signature moves (
fix(spec)!:); see the README's Stability guarantees.
Style
- Conventional commits; commits and tags are signed.
- No generated-with footers, co-author trailers, or session links in commits, PRs, or issues.
- No em dashes in drafted prose; public comments are short.
- Claims in docs must be verifiable: a channel, artefact, or number is only documented once it actually exists.
Off-limits without explicit maintainer direction
- Force pushes, history rewrites, tag deletion or re-tagging.
- Publishing to any registry.
- Changing MSRV, feature flags, or the public API surface.
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.
- 5d ago First seen · 49 lines · 485 tokens per session scan A 359c40e19501
noyalib AGENTS.md is an instructions file published in the GitHub repository sebastienrousseau/noyalib (9 stars, last pushed yesterday), licensed Apache-2.0. It adds 485 tokens to every session, about $0.0024 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-09-05.
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).
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.
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.