Borrowing it
Nothing to install: this file belongs to Ju571nK/sigil. 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/Ju571nK/sigil/main/AGENTS.mdgit clone --depth 1 https://github.com/Ju571nK/sigilWrote 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/ju571nk/sigil/agents-md)<a href="https://agentmods.dev/instructions/ju571nk/sigil/agents-md"><img src="https://agentmods.dev/badge/instructions/ju571nk/sigil/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/ju571nk/sigil/agents-md"><img src="https://agentmods.dev/badge/instructions/ju571nk/sigil/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.00425 | $0.00425 |
| Opus 5.5 | $0.00170 | $0.00170 |
| Sonnet 5.5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
sigil 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 7d 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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Imported Claude Cowork project instructions
GitHub Issue Triage
- Conserve tokens when inspecting GitHub issues: request only the fields and number of results needed for the task, then summarize rather than reproducing full issue bodies.
- A lower-cost model may be used for routine issue discovery, classification, and status summaries. Use a stronger model when implementation planning, security analysis, or conflicting requirements require deeper reasoning.
Generative AI Compatibility Gate
- Before implementing any issue tied to a generative AI product, verify that product's current behavior using official documentation, release notes, and the locally installed version when available.
- Record changes to configuration paths and precedence, permission or approval modes, hook events and payloads, MCP/tool behavior, unattended modes, and platform-specific behavior before changing code.
- Distinguish documented behavior from hardware-verified behavior. Do not remove compatibility gates or enable enforcement from documentation alone when the repository records conflicting measurements.
- Use a lower-cost model for broad changelog discovery and classification, then use a stronger model to validate security implications, resolve contradictions, and define implementation scope.
- Keep research scoped per product and date-stamped so later issue work can reuse it without repeating full discovery.
Sigil Proxy Agent Workflow
For Sigil Proxy work, read the specification entry point, agent roles and operating rules, and current execution status before starting.
- The primary assistant is the orchestrator and the user's single reporting interface.
- Delegate scoped research, coding, independent review, and verification as the authorized task requires.
- Role definitions are not running agents; start workers only for concrete tasks and respect runtime limits.
- Assign one writer per file; link assignments and results to requirement and acceptance IDs.
- Preserve compatibility gates and distinguish implementation, review, and hardware verification.
- Maintain execution status and report integrated results to the user.
- Read sigil-manager's own repository instructions before assigning work there.
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.
- 7d ago First seen · 29 lines · 425 tokens per session scan A 32fb01151370
sigil AGENTS.md is an instructions file published in the GitHub repository Ju571nK/sigil (14 stars, last pushed today), licensed Apache-2.0. It adds 425 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-11.
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.
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.
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).