core github-practices.instructions.md

Repository instructions for GitHub work in navig-run, including a rule that each pull request handles one issue.

In plain words
What is it for?
They are for following the repository's pull-request practices, including what is required, forbidden, and why.
Why use it?
They give an coding agent project-specific rules for preparing and reviewing changes on GitHub.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/navig-run/core/github-practices
Clone the repo
git clone --depth 1 https://github.com/navig-run/core

Made for: GitHub Copilot.

Per session 1,739 This file is loaded in full into every session.
When invoked 1,739 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.01739 $0.01739
Opus 5 $0.00870 $0.00870
Sonnet 5 $0.00348 $0.00348
Haiku 4.5 $0.00174 $0.00174

Measured yesterday against content hash 7ad7cd9e33fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

core github-practices.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 yesterday.

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/instructions/github-practices.instructions.md · 215 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. yesterday First seen · 215 lines · 1,739 tokens per session scan A 7ad7cd9e33fc

Subscribe to this mod's changes

core github-practices.instructions.md is an instructions file published in the GitHub repository navig-run/core (5 stars, last pushed 16d ago), with no licence file. It adds 1,739 tokens to every session, about $0.0087 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.