Borrowing it
Nothing to install: this file belongs to kstep-dev/kstep. 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/kstep-dev/kstep/master/AGENTS.mdgit clone --depth 1 https://github.com/kstep-dev/kstepWrote 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/kstep-dev/kstep/agents-md)<a href="https://agentmods.dev/instructions/kstep-dev/kstep/agents-md"><img src="https://agentmods.dev/badge/instructions/kstep-dev/kstep/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/kstep-dev/kstep/agents-md"><img src="https://agentmods.dev/badge/instructions/kstep-dev/kstep/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.00798 | $0.00798 |
| Opus 5.5 | $0.00319 | $0.00319 |
| Sonnet 5.5 | $0.00160 | $0.00160 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
kstep 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl -sL https://lore.kernel.org/lkml/<email_id>/t.mbox.gz | gunzip` How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Reproduction
To reproduce a bug fixed in commit [hash], follow these steps:
Planning Stage
- Check out the Linux source code just before the fix:
./kstep.sh checkout [hash]~1 [name]_buggy --git. - Read the commit message and patch carefully:
git -C build/master show -U32 [hash]. - Carefully analyze the changes introduced in the patch, focusing on modifications in
build/master/kernel/sched. Trace the call chain that leads to the bug, ensuring you understand the purpose of each function and how they interact. Clearly identify the conditions and system state required to trigger the bug. - If the commit message contains links, carefully review the content of ALL links as they may provide the additional information about the bug (especially the reproduction conditions). For LKML links (e.g.,
lore.kernel.org,lkml.kernel.org,patch.msgid.link), extract the email ID and retrieve the message with:
curl -sL https://lore.kernel.org/lkml/<email_id>/t.mbox.gz | gunzip - Thoughtfully analyze the conditions and mechanisms that trigger the bug, and plan an effective method to reproduce it within the kernel.
Development Stage
- Create a driver in
kmod/drivers_generated/[driver_name].cthat triggers the bug. - Do not leave the driver broken. There could be other agents running with you.
- Guard the driver with
#if LINUX_VERSION_CODEto the compatible kernel version. if unsure, just to the current version you are using. - Try not to directly manipulate internal scheduler state.
- Add detailed logging in your driver for all relevant fields to aid debugging. If necessary, add kernel-side logging with
printk(). - Build and execute the driver on the buggy kernel with:
./kstep.sh checkout [hash]~1 [name]_buggy --git && ./kstep.sh run [name]_buggy [driver_name] - Determine whether the bug is reproduced by examining the output logs:
cat results/latest/kernel.logandresults/latest/kstep.jsonl - If you do not observe the bug, refine your implementation and repeat the process.
- After confirming that your driver triggers the bug, rerun the same driver on the fixed kernel:
./kstep.sh checkout [hash] [name]_fixed --git && ./kstep.sh run [name]_fixed [driver_name] - Review the logs to ensure the bug no longer occurs. In rare cases where the issue persists despite the fix, provide clear documentation and report your findings.
Refinement Stage
- If you manually altered internal scheduler state to trigger the bug during the triggering stage, refine your driver to reproduce the bug using only public kernel APIs or kSTEP interfaces (
kmod/driver.h). If needed, consider extending kSTEP to provide the required functionality. - Make sure that the driver is deterministic, and produce the same trace on the same kernel. If not, investigate the root cause of the non-determinism.
- After confirming your driver can trigger the bug, clearly demonstrate its impact through externally observable behavior, such as changes in task scheduling, rather than relying solely on kernel-internal state.
- Once complete, add an entry for your driver to
bugs.yaml(withextra: true) to enable automated testing.
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 Changed · -4 tokens per session 5b1b0cf76bba
- 1mo ago Changed · +6 tokens per session 57db4cb8e9b9
- 2mo ago First seen · 45 lines · 796 tokens per session scan A 1ca350defdbb
kstep AGENTS.md is an instructions file published in the GitHub repository kstep-dev/kstep (12 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 798 tokens to every session, about $0.0032 per session on Opus 5.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-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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.