Borrowing it
Nothing to install: this file belongs to HazelnutParadise/insyra. 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/HazelnutParadise/insyra/main/AGENTS.mdgit clone --depth 1 https://github.com/HazelnutParadise/insyraWrote 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/hazelnutparadise/insyra/agents-md)<a href="https://agentmods.dev/instructions/hazelnutparadise/insyra/agents-md"><img src="https://agentmods.dev/badge/instructions/hazelnutparadise/insyra/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/hazelnutparadise/insyra/agents-md"><img src="https://agentmods.dev/badge/instructions/hazelnutparadise/insyra/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.15144 | $0.15144 |
| Opus 5.5 | $0.06058 | $0.06058 |
| Sonnet 5.5 | $0.03029 | $0.03029 |
| Haiku 4.5 | $0.01514 | $0.01514 |
Grade A, and why
insyra 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 24d 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 — 444 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file is the primary guidance for AI coding agents working in this repository. CLAUDE.md re-exports it via @AGENTS.md.
What This Repo Is
Insyra (github.com/HazelnutParadise/insyra) is a Go data analysis library (v0.3.x, "Huashan") providing:
DataListandDataTableas the core data structures- CCL (Column Calculation Language) — a domain-specific expression language for column transforms
- A CLI/REPL (
insyrabinary) built with Cobra - Sub-packages for stats, plotting, LP, Python interop, parallel processing, file I/O, etc.
Required artifacts
Each entry says when reading it stops being optional. That trigger is the part that only exists here — the files describe their own contents.
ENG.md— the project's standing technical decisions: architecture, test seams, the precision contract, the measured thresholds, the assumptions everything rests on. Read it before changing architecture, choosing a test seam, deciding what precision something runs at, or writing a migration. Do not re-derive any of it from scratch; if a decision there is wrong, change it there.delivery-status.md— where the project currently stands: phase, blockers, next output, next ticket. Read it first on arrival. It is deltas only, not a roadmap or a changelog.openspec/changes/— the tickets. Pick up anything whose blockers are all done; the milestone order indelivery-status.mdcarries the blocking edges, because OpenSpec has none between changes. Completed changes live inarchive/.
Change Workflow — OpenSpec (required)
Every non-trivial change goes through the OpenSpec workflow. This repo is
OpenSpec-initialized (see openspec/). Do NOT implement a feature, breaking
change, new package, or substantial fix straight into the code — drive it
through a change first:
- Propose — create the change (proposal + spec deltas + tasks) under
openspec/changes/<change-id>/(openspec-propose/openspec-new-change). - Apply — implement the tasks (
openspec-apply-change). - Verify — confirm the implementation matches the artifacts
(
openspec-verify-change). - Archive — once the change is implemented and merged, archive it into
openspec/changes/archive/(openspec-archive-change). Completed changes must be archived, not left sitting inopenspec/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.
- 24d ago Changed · +57 lines · +3,707 tokens per session 169b6eff093c
- 28d ago Changed · +109 lines · +5,981 tokens per session 03307c025a9a
- 1mo ago Changed · +79 tokens per session 4df28504eb04
- 1mo ago First seen · 278 lines · 5,377 tokens per session scan A a9778431df2c
insyra AGENTS.md is an instructions file published in the GitHub repository HazelnutParadise/insyra (57 stars, last pushed yesterday), licensed MIT. It adds 15,144 tokens to every session, about $0.0606 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-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.