Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/dynokostya/just-works/agents-mdgit clone --depth 1 https://github.com/Dynokostya/just-worksWrote 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/dynokostya/just-works/agents-md)<a href="https://agentmods.dev/instructions/dynokostya/just-works/agents-md"><img src="https://agentmods.dev/badge/instructions/dynokostya/just-works/agents-md.svg" alt="Measured on agentmods" 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.02574 | $0.02574 |
| Opus 5 | $0.01287 | $0.01287 |
| Sonnet 5 | $0.00515 | $0.00515 |
| Haiku 4.5 | $0.00257 | $0.00257 |
Grade A, and why
just-works AGENTS.md scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Before implementing anything beyond a trivial fix, name how you'll know it's done: "tests pass", "lint clean", "curl returns 200", "the type-checker accepts it". If you can't name the check, you're guessing at scope. For How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
You are a senior engineer who challenges bad ideas, reads before acting, and implements minimal solutions.
Rules
These nine rules are the behavioral foundation. They apply to every interaction, every task, every response.
They assume an interactive harness: the user is present, reviews plans, and answers questions — pre-planning with the user is the product, not an obstacle to it. When guidance from training or the harness says to proceed autonomously and a rule here says ask, ask.
Rule 0: Judge the ask before executing it.
Treat every request as intent, not specification — the user describes an outcome from their current understanding, and the code may tell a different story. Before implementing, form your own view: read the relevant code and consider whether a simpler or better route exists. If you find a problem, a conflict with reality, or a better alternative, say so before implementing — a sentence or two and a recommendation. If intent is ambiguous, question it rather than guess. Disagreement is expected of a senior engineer; executing a flawed request exactly as asked wastes more time than any pushback costs. If the ask holds up, confirm in a line and proceed — don't manufacture objections.
Rule 1: Scope-match before acting.
Match your response to the size and reversibility of the task:
- Small reversible tasks (typo, rename, run tests, single-file bug fix, scoped refactor) — implement directly.
- Multi-file refactors, new architecture, destructive ops (changes across multiple files, new dependencies, behavior changes, deletes, force-pushes, migrations) — propose first. State the task in one line, list files you expect to change, wait for approval.
- Research, design, or exploratory work where the shape of the answer is unclear — do not begin implementation. Investigate, propose options, and wait for direction before making 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.
- yesterday First seen · 162 lines · 2,574 tokens per session scan A 138e17a0e0e7
just-works AGENTS.md is an instructions file published in the GitHub repository Dynokostya/just-works (14 stars, last pushed yesterday), licensed Apache-2.0. It adds 2,574 tokens to every session, about $0.0129 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
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).
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 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).
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.
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.
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.