agentmods.dev

cc-haha copilot-instructions.md

A short set of coding instructions for the NanmiCoder/cc-haha repository. It requires agents to follow the repository’s AGENTS.md files and the nearest rules for the code they edit.

In plain words
What is it for?
Use it for features, bug fixes, refactoring, or workflow changes that touch this repository, especially when tests, coverage, permissions, or release rules apply.
Why use it?
It helps keep changes consistent with project conventions and ensures that local instructions are not overlooked.

Instructions file for GitHub Copilot

14k +12 today A scan 620 tokens original MIT
View the source file NanmiCoder/cc-haha
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/nanmicoder/cc-haha/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/NanmiCoder/cc-haha

Made for: GitHub Copilot.

Per session 620 This file is loaded in full into every session.
When invoked 620 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00620 $0.00620
Opus 5 $0.00310 $0.00310
Sonnet 5 $0.00124 $0.00124
Haiku 4.5 $0.00062 $0.00062

Measured 2d ago against content hash 395f41471b6c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cc-haha 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 2d 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 · 20 lines

What it actually says

AI Coding Instructions

Follow the root AGENTS.md and the nearest nested AGENTS.md for the files you edit.

For every feature, bugfix, refactor, or workflow change:

  • Treat tool access as capability, not authorization. Do not commit, push, open/merge a PR, release, run live providers, or change repository settings unless explicitly requested.
  • Inspect git status --short, identify the changed surface, define the intended behavior and failure signal, and inspect the nearest implementation and tests before editing.
  • Identify the changed surface before coding: desktop, server/runtime, adapter, native, docs, provider/runtime, agent-loop, persistence, policy/ci, or release.
  • Add same-area tests with the production change. Do not leave production behavior untested unless the PR explicitly carries the maintainer override allow-missing-tests.
  • Preserve or improve the coverage ratchet. New or changed executable production lines must pass the changed-line coverage threshold in scripts/quality-gate/coverage-thresholds.json; do not edit coverage baselines or thresholds without maintainer approval via allow-coverage-baseline-change.
  • Use unit tests for pure logic, API/request-shape tests for server/provider/runtime behavior, Testing Library/Vitest for desktop UI and stores, and E2E or desktop UI smoke for user-visible cross-boundary flows.
  • Ad-hoc browser automation (manual verification, screenshots, exploratory UI checks) goes through the ego-browser skill. The agent-browser binary is reserved for the committed check:desktop-ui-smoke lane and desktop/scripts/e2e-*-agent-browser.sh; do not reach for it as a general browser tool.
  • Provider/auth/runtime-env/model-window/proxy changes require offline bun run check:provider-contract; desktop chat/WebSocket/session-runtime changes require bun run check:chat-contract.
  • Required PR evidence must be deterministic: use fake credentials, temporary config/home paths, mocked or loopback transports, explicit cleanup, and restored environment state. Never call a real provider or use saved machine credentials in required tests.
  • For agent loop, tool execution, provider routing, model selection, file editing, permissions, session resume, and desktop chat changes, include mock/fixture/contract tests. Live smoke is trusted-maintainer evidence only and requires explicit authorization; finding local credentials is not authorization.
  • Run the focused regression first, then bun run check:impact and every selected surface/contract check. Run bun run verify only before claiming PR-ready/push-ready or when full validation was requested.
  • Do not present skipped, blocked, not-run, mock, build-only, or stale evidence as passed live/runtime verification.
  • In the final handoff or PR description, include changed files, tests added, commands actually run with pass/fail counts, checks not run, coverage report path when generated, deterministic E2E evidence, live report path or explicit maintainer-only deferral, and known residual risk.
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. 2d ago First seen · 20 lines · 620 tokens per session scan A 395f41471b6c

Subscribe to this mod's changes

cc-haha copilot-instructions.md is an instructions file published in the GitHub repository NanmiCoder/cc-haha (14,259 stars, last pushed today), licensed MIT. It adds 620 tokens to every session, about $0.0031 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-30.

agentaiai-agentanthropicclaudeclaude-code
Related

Other instructions, from other repositories

ii-agent AGENTS.md

Instructions for Intelligent-Internet/ii-agent, covering ii-agent contributor guide, quick start, repository map, mandatory rules and architecture.

Intelligent-Internet/ii-agent · 3,294 tokens

intelligent-terminal rust.instructions.md

Concise Rust coding conventions for this repository.

microsoft/intelligent-terminal · 435 tokens

InvestSkill GEMINI.md

Instructions for yennanliu/InvestSkill, covering investskill — gemini cli setup & usage guide, installation & setup, quick start, navigate to the investskill directory and start gemini cli (loads gemini.md automatically).

yennanliu/InvestSkill · 3,074 tokens

sortie copilot-instructions.md

Instructions for sortie-ai/sortie, covering sortie coding & review standards, 1. layered imports (downward only; violation is critical), 2. concurrency safety, 3. workspace path safety (critical: security boundary) and 4. persistence (sqlite).

sortie-ai/sortie · 1,030 tokens

crust AGENTS.md

Instructions for chenxin-yan/crust, covering tests, documentation, changesets, agent skills and issue tracker.

chenxin-yan/crust · 388 tokens

she-love-me CLAUDE.md

Instructions for 863401402/she-love-me, covering claude.md and 唯一工作流.

863401402/she-love-me · 268 tokens