Borrowing it
Nothing to install: this file belongs to NarratorAI-Studio/narrator-ai-cli. 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/NarratorAI-Studio/narrator-ai-cli/main/AGENTS.mdgit clone --depth 1 https://github.com/NarratorAI-Studio/narrator-ai-cliWrote 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/narratorai-studio/narrator-ai-cli/agents-md)<a href="https://agentmods.dev/instructions/narratorai-studio/narrator-ai-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/narratorai-studio/narrator-ai-cli/agents-md.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.08023 | $0.08023 |
| Opus 5 | $0.04012 | $0.04012 |
| Sonnet 5 | $0.01605 | $0.01605 |
| Haiku 4.5 | $0.00802 | $0.00802 |
Grade A, and why
narrator-ai-cli 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 7d 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 — 669 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GridLtd Organization Rules
This file is auto-synced to all repositories across the enterprise. Do not edit directly — update the source at Gridltd-DevOps/.github/org-rules.md
Team Directory
When you need to look up team members, fetch the current internal team directory before acting:
gh api repos/Gridltd-DevOps/.github/contents/team/members.yml -q '.content' | base64 -d
Identity rules:
githubis the stable GitHub login. Use it for GitHub operations: assign issues/PRs, request reviews, mention users, CODEOWNERS, branch/commit attribution checks.lark_open_idis the stable Feishu/Lark user id. Use it for Feishu direct messages or user mentions.emailis the stable email destination. Use it for mail only.github_nameis GitHub display metadata and is not stable or guaranteed unique.alias,name,role,responsibility, andprofileare human-readable metadata only; never use them directly as external action identifiers.
If the user gives only a name, alias, display name, role, or other ambiguous
human label, resolve it against team/members.yml first. If more than one
member matches, or if the match depends on memory rather than the current file,
pause and ask the user to confirm the exact github, lark_open_id, or
email before taking any external side effect.
Preferred deterministic resolver:
python .github/workflows/scripts/members/resolve_team_member.py --members-file team/members.yml --query "<name-or-alias-or-login>"
Use --check before changing the directory or agent identity rules:
python .github/workflows/scripts/members/resolve_team_member.py --members-file team/members.yml --check
Organization Standards
Communication
- Communicate in Chinese, keep technical terms in English
- Commit messages and PR descriptions must be in English
Git Flow Branching Model
| Branch | Purpose | Merges to |
|---|---|---|
main |
Production-ready code, always stable | — |
develop |
Integration branch for features | main (via release) |
feature/<issue-id>-<short-desc> |
New features | develop |
release/<version> |
Release preparation & QA | main + develop |
hotfix/<issue-id>-<short-desc> |
Urgent production fixes | main + develop |
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.
- 7d ago First seen · 669 lines · 8,023 tokens per session scan A 88f706dea86a
narrator-ai-cli AGENTS.md is an instructions file published in the GitHub repository NarratorAI-Studio/narrator-ai-cli (127 stars, last pushed 1mo ago), licensed MIT. It adds 8,023 tokens to every session, about $0.0401 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.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.