Borrowing it
Nothing to install: this file belongs to norton77930/corpus-ingest-core. 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/norton77930/corpus-ingest-core/main/AGENTS.mdgit clone --depth 1 https://github.com/norton77930/corpus-ingest-coreWrote 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/norton77930/corpus-ingest-core/agents-md)<a href="https://agentmods.dev/instructions/norton77930/corpus-ingest-core/agents-md"><img src="https://agentmods.dev/badge/instructions/norton77930/corpus-ingest-core/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.00729 | $0.00729 |
| Opus 5 | $0.00365 | $0.00365 |
| Sonnet 5 | $0.00146 | $0.00146 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
corpus-ingest-core 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 8d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Agent Instructions
New agents: start with docs/agent-handoff.md (10-minute repo handoff, boundaries mapped to guard tests) and docs/ai-development-framework.md (instruction hierarchy, change classification, completion report format). The Engineering Rules below are hard constraints and remain authoritative.
This repository uses Spec Kit with Codex skills. For new feature work, prefer the Spec Kit flow before implementation:
$speckit-constitutionto establish or amend project principles.$speckit-specifyto create or update user-facing requirements.$speckit-clarifyto resolve high-impact ambiguity before planning.$speckit-planto create the technical plan.$speckit-checklistto create feature-specific quality and safety checks.$speckit-tasksto break the plan into actionable work.$speckit-analyzeto check spec, plan, and tasks for consistency before implementation.$speckit-implementto execute approved tasks.$speckit-convergeto compare code against spec, plan, and tasks after implementation and add missing work.
Use $speckit-taskstoissues only when GitHub issue handoff is needed. The normal full Spec Kit flow is:
constitution -> specify -> clarify -> plan -> checklist -> tasks -> analyze -> implement -> converge
This repository contains multiple as-built Spec Kit packages and does not pin
a single active feature. Before running official Spec Kit scripts or skills,
set SPECIFY_FEATURE_DIRECTORY to the selected package and follow the
selection guidance in specs/README.md. A historical
reference such as
specs/019-episode-verified-research-report-workflow/plan.md
describes completed work only; it is not an active-feature selector.
The current in-progress package plan is
specs/042-workflow-derivation-bundle/plan.md;
select it explicitly with SPECIFY_FEATURE_DIRECTORY — do not treat that
path as a repository-wide active-feature pin.
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.
- 8d ago First seen · 60 lines · 729 tokens per session scan A 880ec0e93d26
corpus-ingest-core AGENTS.md is an instructions file published in the GitHub repository norton77930/corpus-ingest-core (2 stars, last pushed 8d ago), licensed MIT. It adds 729 tokens to every session, about $0.0036 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).
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.
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.