Borrowing it
Nothing to install: this file belongs to CGSOG-JumpStarts/JumpStart-AutoNav. 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/CGSOG-JumpStarts/JumpStart-AutoNav/main/.github/instructions/specs.instructions.mdgit clone --depth 1 https://github.com/CGSOG-JumpStarts/JumpStart-AutoNavWrote 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/cgsog-jumpstarts/jumpstart-autonav/specs)<a href="https://agentmods.dev/instructions/cgsog-jumpstarts/jumpstart-autonav/specs"><img src="https://agentmods.dev/badge/instructions/cgsog-jumpstarts/jumpstart-autonav/specs/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/cgsog-jumpstarts/jumpstart-autonav/specs"><img src="https://agentmods.dev/badge/instructions/cgsog-jumpstarts/jumpstart-autonav/specs.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.00515 | $0.00515 |
| Opus 5 | $0.00258 | $0.00258 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
JumpStart-AutoNav specs.instructions.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 10d 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
Jump Start Spec Artifact Guidelines
When editing or generating files in the specs/ directory:
- Always use the corresponding template from
.jumpstart/templates/as the starting structure. - Never leave bracket placeholders like
[DATE]or[description]in the final version. Replace them with real content. - Every artifact must have a populated Phase Gate Approval section at the bottom.
- Maintain traceability: every Must Have item should reference upstream artifacts (e.g., a PRD story references a Product Brief capability, which references a Challenger Brief validation criterion).
- Use Markdown tables for structured data. Keep tables readable.
- Do not introduce content that belongs in a different phase's artifact.
- For brownfield projects,
specs/codebase-context.mduses the template from.jumpstart/templates/codebase-context.md. C4 diagrams use Mermaid syntax. - For greenfield projects, per-directory
AGENTS.mdfiles use the template from.jumpstart/templates/agents-md.md. - Every
specs/architecture.mdmust cover the six core areas: Commands (build/test/lint/deploy with full flags), Testing (framework, location, coverage expectations), Project Structure (directory layout with purpose annotations), Code Style (naming conventions, formatting rules, code examples), Git Workflow (branching, commit format, PR requirements), and Boundaries (three-tier: Always do / Ask first / Never do). Missing areas should be flagged during review. - For specs exceeding 500 lines, include an Extended Table of Contents section with per-section summaries (max 2 sentences each) immediately after the YAML frontmatter. This helps agents and humans quickly locate relevant sections. See
.jumpstart/guides/spec-writing.md§3 for the format. - Agents consuming specs must self-verify their output against the spec's acceptance criteria before presenting for approval. Any unaddressed spec items must be explicitly listed. See
.jumpstart/guides/spec-writing.md§4 for the self-verification protocol. - Spec boundaries must use the three-tier system (Always do / Ask first / Never do). Place boundary sections early in architecture and implementation plan documents so agents encounter constraints before implementation details.
- When a single spec artifact exceeds 800 lines, consider decomposing it into sub-specs (e.g., separate API contract spec, data model spec) and linking them from the parent document with clear cross-references.
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.
- 10d ago First seen · 22 lines · 515 tokens per session scan A 80d2cfe029a2
JumpStart-AutoNav specs.instructions.md is an instructions file published in the GitHub repository CGSOG-JumpStarts/JumpStart-AutoNav (10 stars, last pushed 3mo ago), licensed MIT. It adds 515 tokens to every session, about $0.0026 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.