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.
git 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/plugins/thuanvd378/write-me-a-readme/write-a-readme)<a href="https://agentmods.dev/plugins/thuanvd378/write-me-a-readme/write-a-readme"><img src="https://agentmods.dev/badge/plugins/thuanvd378/write-me-a-readme/write-a-readme/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/plugins/thuanvd378/write-me-a-readme/write-a-readme"><img src="https://agentmods.dev/badge/plugins/thuanvd378/write-me-a-readme/write-a-readme.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
write-a-readme 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.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "write-a-readme",
"version": "0.1.1",
"displayName": "Write Me a README",
"description": "Turn codebases into accurate, on-brand READMEs with editable SVG banners.",
"author": {
"name": "Write Me a README contributors"
},
"license": "MIT",
"skills": "./skills/"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 103 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 13 lines scan A 0e3f3af3e9dd
write-a-readme is a plugin published in the GitHub repository thuanvd378/write-me-a-readme (2 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.
write-a-readme compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| write-a-readmethuanvd378/write-me-a-readme | Plugin | 2 | 3mo ago | MIT | A | — | Claude Code |
| agent-stylebooksNeeeophytee/agent-stylebooks | Plugin | 78 | 2mo ago | MIT | A | — | Claude Code |
| sourcey-docssourcey/sourcey | Plugin | 1.4k | 2d ago | AGPL-3.0 | A | — | Claude Code |
| cloud-sql-sqlservergemini-cli-extensions/cloud-sql-sqlserver | Plugin | 10 | 1mo ago | Apache-2.0 | A | — | Gemini CLI |
| onebrainonebrain-ai/onebrain | Plugin | 31 | 2mo ago | Apache-2.0 | A | — | Claude Code |
| bm-skillsbasemachina/skills | Plugin | 2 | 28d ago | MIT | A | — | Claude Code |
| oat-publish-pythonOpen-Agent-Tools/General-OAT-Skills | Plugin | 3 | 1mo ago | Apache-2.0 | A | — | Claude Code |