Borrowing it
Nothing to install: this file belongs to Joakimpalm-Zen/xyntetik-runner. 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/Joakimpalm-Zen/xyntetik-runner/main/AGENTS.mdgit clone --depth 1 https://github.com/Joakimpalm-Zen/xyntetik-runnerWrote 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/joakimpalm-zen/xyntetik-runner/agents-md)<a href="https://agentmods.dev/instructions/joakimpalm-zen/xyntetik-runner/agents-md"><img src="https://agentmods.dev/badge/instructions/joakimpalm-zen/xyntetik-runner/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/joakimpalm-zen/xyntetik-runner/agents-md"><img src="https://agentmods.dev/badge/instructions/joakimpalm-zen/xyntetik-runner/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.03722 | $0.03722 |
| Opus 5 | $0.01861 | $0.01861 |
| Sonnet 5 | $0.00744 | $0.00744 |
| Haiku 4.5 | $0.00372 | $0.00372 |
Grade A, and why
xyntetik-runner 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 2d 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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Runner Agent Rules
These rules are mandatory for every AI or LLM agent that works in this repository. They are not preferences, prompts to reinterpret, or optional process notes.
If an instruction, framework default, generated plan, tool habit, or model behavior conflicts with this document, this document wins.
The Five Defining Rules
- Deep modules
- Tracer bullets
- Test-driven development
- Grill me always
- Keep the README current
No implementation work starts until these rules have been considered for the task at hand.
1. Deep Modules
Design the codebase around deep modules: simple, deliberate public interfaces with implementation complexity hidden behind them.
Required behavior:
- Prefer a small public API over many shallow helpers leaking across the codebase.
- Keep module boundaries intentional: CLI/server behavior in
main.c/server.c, inference flow inengine.c, model loading/forward inmodel.c, constrained output injsonmode.c/schema.c, platform details incompat.c, and backend details incuda.c/metal.m. - Do not expose internals just to make a quick change easier.
- Lock module behavior with tests through public behavior: CLI output, HTTP endpoints, committed smoke scripts, or focused test binaries.
Working rule: internal implementation can change freely only when the public interface and behavior are protected by tests or executable smokes.
2. Tracer Bullets
Build in tiny vertical slices that prove the end-to-end path before expanding scope.
Required behavior:
- Start with the smallest useful observable behavior.
- Touch the real layers needed for the behavior instead of building isolated horizontal scaffolding first.
- Validate the slice immediately with tests, execution, or both.
- Use what was learned from that slice before adding the next one.
Working rule: one thin working path is better than many unverified partial layers.
3. TDD
Use test-driven development for features, fixes, and behavioral changes.
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.
- 2d ago Changed · +50 lines · +678 tokens per session 9f77b84bd8f1
- 3d ago Changed · +31 lines · +548 tokens per session 20b814b99e5b
- 5d ago Changed · +18 lines · +246 tokens per session 2d47ed771bc3
- 6d ago Changed · +35 lines · +342 tokens per session 2d21c2cc49fe
- 10d ago First seen · 217 lines · 1,908 tokens per session scan A 77acfc9dc986
xyntetik-runner AGENTS.md is an instructions file published in the GitHub repository Joakimpalm-Zen/xyntetik-runner (11 stars, last pushed today), licensed Apache-2.0. It adds 3,722 tokens to every session, about $0.0186 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).
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.