Borrowing it
Nothing to install: this file belongs to 6529-Collections/6529seize-frontend. 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/6529-Collections/6529seize-frontend/main/AGENTS.mdgit clone --depth 1 https://github.com/6529-Collections/6529seize-frontendWrote 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/6529-collections/6529seize-frontend/agents-md)<a href="https://agentmods.dev/instructions/6529-collections/6529seize-frontend/agents-md"><img src="https://agentmods.dev/badge/instructions/6529-collections/6529seize-frontend/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/6529-collections/6529seize-frontend/agents-md"><img src="https://agentmods.dev/badge/instructions/6529-collections/6529seize-frontend/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.05917 | $0.05917 |
| Opus 5.5 | $0.02367 | $0.02367 |
| Sonnet 5.5 | $0.01183 | $0.01183 |
| Haiku 4.5 | $0.00592 | $0.00592 |
Grade A, and why
6529seize-frontend 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 14d 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 — 443 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Deployment
- Follow
ops/skills/deploy-6529/SKILL.mdfor authorized staging and production work, using ordinary Git merges and the existing GitHub Actions workflows. - Before claiming missing maintainer/admin authority or repeating a permission question, follow Verify GitHub authority. Check the authenticated account, repo permissions, actual required team and effective rules; preserve existing explicit authorization for the release.
- For staging, merge the development branch into the latest
1a-stagingand push. Frontend changes automatically startWeb Deploy - STAGING; backend changes require dispatchingDeploy a servicefor the required services. - For production, merge the development branch into
main, then dispatchWeb Deploy - PRODfor frontend orDeploy a servicewithenvironment=prodfor backend. A staging request alone does not authorize production. - Run backend service deployments sequentially in dependency order. Wait for each run to succeed, then continue the next service in the same task without asking for repeated authorization already covered by the requested phase.
- Deploy backend dependencies before merging or deploying dependent frontend changes in each environment. Read the backend service catalog and the change to determine the units and order; avoid deploying unrelated services.
- Fetch shared refs before merging. Preserve other developers' changes, resolve conflicts normally, and never force-push or overwrite a moved shared ref. Do not cancel another developer's deployment; coordinate through GitHub run visibility and wait when the work would conflict.
- Complete deployments after build, artifact integrity, runtime version, and health checks pass. Automatic E2E runs separately and does not hold up a merge, deployment, or promotion to the next authorized environment.
- Unrelated PR E2E failures or pending runs do not block releases. Keep relevant build, unit/contract, and security checks intact; report E2E status separately. Fix known regressions attributable to the change on the development branch.
- CI wave notifications carry deploy run IDs through E2E and reruns. The backend alone resolves the drop reply target; notification failures remain best effort. Keep receiver and sender contracts compatible during rollout.
- Never author or post release notes manually. Preserve the autonomous bot's PR/service grouping metadata and final publication signal; use the release-note opt-out only when the user explicitly requests suppressing release notes.
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.
- 14d ago Changed · +2 lines · +90 tokens per session 3e6b1650bc91
- 15d ago Changed · -4 lines · -68 tokens per session 744558e12cca
- 18d ago Changed · +5 lines · +123 tokens per session 2d90288fcb4e
- 1mo ago Changed · +52 lines · +685 tokens per session 5cde2ef462f8
- 1mo ago Changed · +4 lines · +68 tokens per session 58d07377b515
- 1mo ago Changed · +26 lines · +356 tokens per session 95493279d991
- 1mo ago Changed · +8 lines · +133 tokens per session b3e52bcb4bf7
- 1mo ago Changed · +3 lines · +41 tokens per session 92e086f1512f
- 1mo ago Changed · -49 lines · -762 tokens per session 11fd5dcca66d
- 2mo ago First seen · 396 lines · 5,251 tokens per session scan A 7d078f64df85
6529seize-frontend AGENTS.md is an instructions file published in the GitHub repository 6529-Collections/6529seize-frontend (10 stars, last pushed today), licensed Apache-2.0. It adds 5,917 tokens to every session, about $0.0237 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-31.
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.