Borrowing it
Nothing to install: this file belongs to thuanvd378/write-me-a-readme. 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/thuanvd378/write-me-a-readme/main/AGENTS.mdgit clone --depth 1 https://github.com/thuanvd378/write-me-a-readmeWrote 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/thuanvd378/write-me-a-readme/agents-md)<a href="https://agentmods.dev/instructions/thuanvd378/write-me-a-readme/agents-md"><img src="https://agentmods.dev/badge/instructions/thuanvd378/write-me-a-readme/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/thuanvd378/write-me-a-readme/agents-md"><img src="https://agentmods.dev/badge/instructions/thuanvd378/write-me-a-readme/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.00445 | $0.00445 |
| Opus 5.5 | $0.00178 | $0.00178 |
| Sonnet 5.5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
write-me-a-readme 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 2mo 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository guidance
Source of truth
- The canonical skill is
plugins/write-a-readme/skills/readme/. - Keep the skill name
readmeand its folder name identical. - Treat files under
adapters/andplugins/write-a-readme/commands/as thin invocation adapters; do not duplicate the full workflow there. - Keep Codex plugin metadata in
plugins/write-a-readme/.codex-plugin/plugin.jsonaligned withSKILL.mdandagents/openai.yaml. - Keep Claude plugin metadata in
plugins/write-a-readme/.claude-plugin/plugin.json; the repository-root.claude-plugin/marketplace.jsononly catalogs it.
Content rules
- Derive README guidance from repository evidence and cited first-party sources.
- Do not copy README prose, banners, screenshots, icons, or brand assets from example repositories.
- Do not claim that any output guarantees SEO rank, GitHub Trending placement, stars, or adoption.
- Record a source page, author, license, restrictions, retrieval date, and modifications for every downloaded visual.
- Keep core
SKILL.mdconcise. Put detailed, conditionally loaded guidance one level down inreferences/.
Implementation rules
- Support Python 3.10 or newer.
- Keep project inspection and README validation standard-library-only.
- Keep banner rendering limited to Pillow plus the standard library.
- Keep unit tests offline and deterministic; mock network responses.
- Reject path traversal, active SVG content, remote final assets, secret-bearing files, and silent overwrite by default.
Verification
Run from the repository root:
python -m pip install -r plugins/write-a-readme/skills/readme/requirements.txt
python -m unittest discover -s tests -v
python C:/Users/ADMIN/.codex/skills/.system/skill-creator/scripts/quick_validate.py plugins/write-a-readme/skills/readme
python C:/Users/ADMIN/.codex/skills/.system/plugin-creator/scripts/validate_plugin.py plugins/write-a-readme
The last two paths are local Codex development helpers and are not assumed to exist in public CI.
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.
- 2mo ago First seen · 39 lines · 445 tokens per session scan A 6ab4025d97d7
write-me-a-readme AGENTS.md is an instructions file published in the GitHub repository thuanvd378/write-me-a-readme (2 stars, last pushed 3mo ago), licensed MIT. It adds 445 tokens to every session, about $0.0018 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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.