agentmods.dev

ReactSentinel: Instructions file for GitHub Copilot

.github/copilot-instructions.md

ReactSentinel copilot-instructions.md is an instructions file for GitHub Copilot from edgarbnt/ReactSentinel. It costs 741 tokens per session, scanned A, original, MIT.

Project instructions define an autonomous workflow for completing a software sprint through GitHub, Jira, and coding tools. Jira is a system for tracking work items, while a branch is an isolated line of code changes.

In plain words
What is it for?
Use them to identify sprint tickets, choose their order, create one sprint branch, update Jira through its connected tools, implement the work, run tests, and document delivery.
Why use it?
They give the agent a fixed order of operations and require progress updates, evidence, and a single shared branch, reducing confusion during multi-ticket work.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is edgarbnt/ReactSentinel's own configuration. It tells GitHub Copilot how to work on ReactSentinel itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ReactSentinel configures →

not rated 1repo 5mo ago A scan 741 tokens original MIT
View source ↗ edgarbnt/ReactSentinel
Reuse

Borrowing it

Nothing to install: this file belongs to edgarbnt/ReactSentinel. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/edgarbnt/ReactSentinel/main/.github/copilot-instructions.md
Clone the repo
git clone --depth 1 https://github.com/edgarbnt/ReactSentinel

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for ReactSentinel copilot-instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/edgarbnt/reactsentinel/copilot-instructions/github.svg)](https://agentmods.dev/instructions/edgarbnt/reactsentinel/copilot-instructions)
Your own site
<a href="https://agentmods.dev/instructions/edgarbnt/reactsentinel/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/edgarbnt/reactsentinel/copilot-instructions/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.

agentmods 80×15 button for ReactSentinel copilot-instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/edgarbnt/reactsentinel/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/edgarbnt/reactsentinel/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 741 This file is loaded in full into every session.
When invoked 741 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00741 $0.00741
Opus 5.5 $0.00296 $0.00296
Sonnet 5.5 $0.00148 $0.00148
Haiku 4.5 $0.00074 $0.00074

Measured 1mo ago against content hash 0da827babcbf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

.github/copilot-instructions.md · 56 lines

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-atlassian server 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

  1. Planning: Identify all parent tickets for the sprint.
  2. Sequencing: Validate the execution order (via Jira ID, priority, or logical dependencies).
  3. Branching: Create the unique sprint branch from the reference branch (main or develop).
  4. 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-atlassian to 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.

Read the full file on GitHub · 56 lines

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.

  1. 1mo ago First seen · 56 lines · 741 tokens per session scan A 0da827babcbf

Subscribe to this mod's changes

ReactSentinel copilot-instructions.md is an instructions file published in the GitHub repository edgarbnt/ReactSentinel (1 stars, last pushed 5mo ago), licensed MIT. It adds 741 tokens to every session, about $0.0030 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.

Claude CodeProject managementai-agentsbrowser-automationcopilotcursor
Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

vscode model-prompts.instructions.md

Model-specific prompt authoring and registry guidelines.

microsoft/vscode · 2,022 tokens