Borrowing it
Nothing to install: this file belongs to rarce/git-wiki. 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/rarce/git-wiki/main/AGENTS.mdgit clone --depth 1 https://github.com/rarce/git-wikiWrote 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/rarce/git-wiki/agents-md)<a href="https://agentmods.dev/instructions/rarce/git-wiki/agents-md"><img src="https://agentmods.dev/badge/instructions/rarce/git-wiki/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/rarce/git-wiki/agents-md"><img src="https://agentmods.dev/badge/instructions/rarce/git-wiki/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.00672 | $0.00672 |
| Opus 5.5 | $0.00269 | $0.00269 |
| Sonnet 5.5 | $0.00134 | $0.00134 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
git-wiki 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 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This repository distributes the git-wiki Agent Skill and its installer.
Root-level files are project documentation and entry points: README.md,
install.sh, LICENSE, and assets/demo.gif. The skill lives in
skills/git-wiki/: SKILL.md defines behavior and trigger rules,
scripts/setup.sh scaffolds a user's wiki repository, and
assets/wiki-scaffold/ contains Markdown templates copied into that wiki
(CLAUDE.md, index.md, log.md, README.md, and gitattributes).
Build, Test, and Development Commands
bash -n install.shchecks installer shell syntax.bash -n skills/git-wiki/scripts/setup.shchecks the wiki scaffolder syntax.shellcheck install.sh skills/git-wiki/scripts/setup.shruns shell linting when ShellCheck is available.bash install.shruns the full interactive installer, creating or reusing a wiki repo. UseWIKI_VIS=localto avoid GitHub publishing; other modes exercise GitHub andnpxside effects.qmdmust already be installed.
Coding Style & Naming Conventions
Shell scripts use Bash with set -euo pipefail, small helper functions
(say, warn, die, require), uppercase environment variables, and
lowercase local variables. Keep scripts POSIX-friendly where practical, but
preserve Bash when existing code depends on it. Markdown files use concise
headings, fenced sh examples, and relative links. Wiki page and scaffold file
names should be lowercase kebab-case where generated content needs names.
Testing Guidelines
There is no automated test harness. For script changes, run both bash -n
commands and ShellCheck if installed. For scaffold changes, review the generated
paths expected by setup.sh, especially skills/git-wiki/assets/wiki-scaffold/.
For installer changes, prefer WIKI_VIS=local for smoke tests. Use a
disposable private GitHub repo and temporary WIKI_DIR only when validating
remote publishing, for example:
WIKI_REPO=tmp-git-wiki WIKI_VIS=private WIKI_DIR=/tmp/tmp-git-wiki bash install.sh.
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.
- 1mo ago First seen · 57 lines · 672 tokens per session scan A ba1965077ebf
git-wiki AGENTS.md is an instructions file published in the GitHub repository rarce/git-wiki (22 stars, last pushed 4mo ago), licensed MIT. It adds 672 tokens to every session, about $0.0027 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-30.
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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.