Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/edgarbnt/reactsentinel/copilot-instructionsgit clone --depth 1 https://github.com/edgarbnt/ReactSentinelWrote 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/edgarbnt/reactsentinel/copilot-instructions)<a href="https://agentmods.dev/instructions/edgarbnt/reactsentinel/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/edgarbnt/reactsentinel/copilot-instructions.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.00741 | $0.00741 |
| Opus 5 | $0.00370 | $0.00370 |
| Sonnet 5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
ReactSentinel copilot-instructions.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 5d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Instructions — Sprint Work (Autonomous Mode, Live Jira & Reporting)
Objective
This document defines the operating procedure for completing an entire sprint autonomously. You must execute all parent tickets sequentially without interruption, keep the Jira board updated in real-time via the Atlassian MCP server, and document the final delivery.
General Principles
- Complete Autonomy: Once the sprint is launched, process all identified tickets one after another without waiting for validation to move to the next one.
- Single Branch: Create one single branch for the entire sprint (e.g.,
sprint/sprint-name). Work exclusively on this branch. - Jira-Driven: Systematically use the
mcp-atlassianserver tools to read ticket details and update their status. - Context-Mode Usage: Prioritize
ctx_*tools for analyzing logs or the codebase. Use Bash only for Git actions and test execution.
Execution Order
- Planning: Identify all parent tickets for the sprint.
- Sequencing: Validate the execution order (via Jira ID, priority, or logical dependencies).
- Branching: Create the unique sprint branch from the reference branch (
mainordevelop). - Continuous Execution: Process parent tickets fluidly and without pauses between tickets.
Workflow per Parent Ticket
For each parent ticket, strictly follow this lifecycle:
1. Jira Update (Start)
- Move the parent ticket and its first sub-task to "In Progress" (or equivalent) via
mcp-atlassian.
2. Implementation and Validation
- Implement sub-tasks one by one.
- After each sub-task:
- Test the functional behavior (not just compilation).
- If successful, use
mcp-atlassianto move the sub-task to the "Done" column. - Make an intermediate commit on the sprint branch.
- A sub-task is only considered finished if its test is validated and its Jira status is updated.
3. Parent Finalization
Once all sub-tasks of a parent are validated:
- Jira Closure: Move the parent ticket to the "Done" column via
mcp-atlassian. - Push: Push the sprint branch to the remote repository to secure progress.
- Transition: Immediately create/start the next parent ticket and repeat from step 1.
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.
- 5d ago First seen · 56 lines · 741 tokens per session scan A 0da827babcbf
ReactSentinel copilot-instructions.md is an instructions file published in the GitHub repository edgarbnt/ReactSentinel (1 stars, last pushed 3mo ago), licensed MIT. It adds 741 tokens to every session, about $0.0037 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
mcp-unity AGENTS.md
AGENTS.md instructions for CoderGamester/mcp-unity, covering mcp unity — ai agent guide (mcp package), purpose (what this repo is), how it works (high-level data flow), key defaults & invariants and repo layout (where to change what).
rails-ai-context AGENTS.md
AGENTS.md instructions for crisnahine/rails-ai-context, covering rails-ai-context, agent skills, issue tracker, triage labels and domain docs.
plugin-files-mode
Rosetta Plugin Mode Bootstrap.
inspecto CLAUDE.md
Claude Code instructions for inspecto-dev/inspecto, covering inspecto — claude code development guide, project overview, monorepo structure, development phases (load each file as needed) and key architectural decisions.
skill.color-expert CLAUDE.md
Claude Code instructions for meodai/skill.color-expert, covering claude.md, project overview, architecture, no build/test/lint and editing guidelines.
llm-ide-rules typescript.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering typescript and dates & times.