Borrowing it
Nothing to install: this file belongs to Enovatr-Labs/SpecRoute. 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/Enovatr-Labs/SpecRoute/main/runtimes/.kiro/steering/README.mdgit clone --depth 1 https://github.com/Enovatr-Labs/SpecRouteWrote 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/enovatr-labs/specroute/readme)<a href="https://agentmods.dev/instructions/enovatr-labs/specroute/readme"><img src="https://agentmods.dev/badge/instructions/enovatr-labs/specroute/readme/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/enovatr-labs/specroute/readme"><img src="https://agentmods.dev/badge/instructions/enovatr-labs/specroute/readme.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.00417 | $0.00417 |
| Opus 5.5 | $0.00167 | $0.00167 |
| Sonnet 5.5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
SpecRoute README.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 3d 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
.kiro/steering/
Steering rules - markdown files Kiro loads as context, either always or matching a file pattern.
Inclusion modes
Always-on
Frontmatter:
---
inclusion: always
---
Loaded into every Kiro conversation. Use sparingly - these eat context budget. Reserve for true cross-cutting rules (engineering standards, security baseline, project structure).
See rules/steering/always-on-template.md for the canonical template.
File-pattern-matched
Frontmatter:
---
inclusion: fileMatch
fileMatchPattern: "src/**/*.tsx"
---
Loaded only when the user is working with a file matching the pattern. Use for vertical-slice rules (frontend conventions, database conventions, secrets handling).
See rules/steering/file-match-template.md for the template.
Suggested files
Map your project's rules into steering files:
| Steering file | Inclusion | Loaded for |
|---|---|---|
engineering-rules.md |
always | every conversation |
code-review-rules.md |
always | every conversation |
security-rules.md |
always | every conversation |
documentation-rules.md |
fileMatch (*.md) |
doc edits |
frontend-rules.md |
fileMatch (src/components/**, src/pages/**) |
frontend edits |
backend-rules.md |
fileMatch (src/services/**) |
backend edits |
secrets-management.md |
fileMatch (*secret*, *vault*, *eso*) |
secrets-touching edits |
Source content
The actual rule content can be sourced from ../../rules/. Either copy the file content directly into a steering file (with the inclusion frontmatter prepended) or symlink. Copying is simpler; symlinks risk Kiro / cross-vendor weirdness.
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.
- 3d ago First seen · 53 lines · 417 tokens per session scan A fbf50b04cbd3
SpecRoute README.md is an instructions file published in the GitHub repository Enovatr-Labs/SpecRoute (3 stars, last pushed 4d ago), licensed Apache-2.0. It adds 417 tokens to every session, about $0.0017 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-10-20.
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.