Borrowing it
Nothing to install: this file belongs to harumiWeb/exstruct. 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/harumiWeb/exstruct/main/AGENTS.mdgit clone --depth 1 https://github.com/harumiWeb/exstructWrote 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/harumiweb/exstruct/agents-md)<a href="https://agentmods.dev/instructions/harumiweb/exstruct/agents-md"><img src="https://agentmods.dev/badge/instructions/harumiweb/exstruct/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/harumiweb/exstruct/agents-md"><img src="https://agentmods.dev/badge/instructions/harumiweb/exstruct/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.01530 | $0.01530 |
| Opus 5.5 | $0.00612 | $0.00612 |
| Sonnet 5.5 | $0.00306 | $0.00306 |
| Haiku 4.5 | $0.00153 | $0.00153 |
Grade A, and why
exstruct 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 26d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ExStruct AI Agents Guide
0. Overview
This repository is organized around the following top-level directories:
exstruct/
|- src/ # Main library and implementation code
|- tests/ # Automated tests
|- sample/ # Sample workbooks and example inputs
|- schemas/ # JSON schemas and validation-related assets
|- scripts/ # Utility and maintenance scripts
|- benchmark/ # Benchmark code and performance measurements
|- docs/ # User-facing documentation
|- dev-docs/ # All developer-facing documentation
|- tasks/ # Temporary task notes and working files
|- drafts/ # Draft documents and work-in-progress materials
|- dist/ # Build artifacts and packaged outputs
`- site/ # Generated documentation site output
For internal development guidance, architecture notes, ADRs, specifications, and testing references, use dev-docs/ as the canonical location. Developer-facing documentation should be written there rather than scattered across the repository.
1. Workflow Design
1. Use Plan mode by default
- Always start tasks with 3 or more steps, or tasks that affect architecture, in Plan mode
- If things stop going well partway through, do not force it; stop immediately and replan
- Use Plan mode not only for implementation, but also for verification steps
- Write detailed specifications before implementation to reduce ambiguity
2. Multi-Agent Strategy
- Actively use sub-agents to keep the main context window clean
- Delegate research, investigation, and parallel analysis to sub-agents
- For complex problems, use sub-agents to apply more compute resources
- To keep execution focused, assign one task per sub-agent
- Use explorer for read-heavy codebase exploration
- Use worker for implementation and fixes
- Use reviewer for reviews
3. Self-Improvement Loop
- Whenever you receive a correction from the user, record that pattern in
tasks/lessons.md - Write rules for yourself so you do not repeat the same mistake
- Keep improving those rules thoroughly until the error rate goes down
- At the start of each session, review the lessons relevant to the project
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.
- 26d ago Changed · -34 lines · -701 tokens per session f772c1c9c2e6
- 2mo ago First seen · 183 lines · 2,231 tokens per session scan A 89fbaf5071ad
exstruct AGENTS.md is an instructions file published in the GitHub repository harumiWeb/exstruct (204 stars, last pushed 26d ago), licensed BSD-3-Clause. It adds 1,530 tokens to every session, about $0.0061 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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.