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.
npx skills add appleweiping/WEIPING_WIKI --skill readme-blueprint-generatorgit clone --depth 1 https://github.com/appleweiping/WEIPING_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/skills/appleweiping/weiping_wiki/readme-blueprint-generator)<a href="https://agentmods.dev/skills/appleweiping/weiping_wiki/readme-blueprint-generator"><img src="https://agentmods.dev/badge/skills/appleweiping/weiping_wiki/readme-blueprint-generator/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/skills/appleweiping/weiping_wiki/readme-blueprint-generator"><img src="https://agentmods.dev/badge/skills/appleweiping/weiping_wiki/readme-blueprint-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00087 | $0.00712 |
| Opus 5 | $0.00044 | $0.00356 |
| Sonnet 5 | $0.00017 | $0.00142 |
| Haiku 4.5 | $0.00009 | $0.00071 |
Grade A, and why
readme-blueprint-generator 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
README Blueprint Generator
Generate or rewrite README.md as the public front door to a repository. The output should feel intentionally designed: clear first impression, strong hierarchy, concrete quick start, and no filler.
Workflow
- Inspect the current README and the project's authoritative docs before rewriting.
- Prefer
AGENTS.md,.wiki-schema.md,purpose.md,CONTRIBUTING.md,WORKFLOWS.md, package metadata, docs indexes, and existing automation scripts when present. - If
.github/copilot/or.github/copilot-instructions.mdexists, read the smallest relevant files for architecture, stack, tests, workflow, and standards.
- Prefer
- Decide the README's audience and job.
- Public reader: what is this, why should they care, where do they go next?
- Maintainer or future agent: how do they start, verify, maintain, and avoid dangerous mistakes?
- Build a narrative outline before editing.
- Start with a crisp identity sentence.
- Put the most important navigation and quick-start material above long reference sections.
- Use tables only when they reduce cognitive load.
- Link to deeper docs instead of duplicating them.
- Rewrite for polish.
- Prefer specific verbs and nouns.
- Remove generic "comprehensive", "powerful", "easy-to-use" language unless backed by concrete behavior.
- Keep sections visually varied: short paragraphs, compact tables, short command blocks, and scannable bullets.
- Avoid overlong catalogs in README; point to maintained indexes.
- Validate the README as an artifact.
- Check that commands are plausible for the repo.
- Check that public/private boundaries are respected.
- Check that the README does not claim unverified features or live status.
- Run the repository's documentation, lint, catalog, or diff hygiene commands when available.
Recommended Structure
Use this only as a starting shape; adapt to the repo.
- Title and one-sentence positioning.
- Short "why it exists" paragraph.
- Entry map or "start here" table.
- Quick start or common commands.
- Architecture or repository map.
- Core workflows.
- Quality gates and verification.
- Contribution or maintenance contract.
- Security/public-private boundaries when relevant.
- Links to deeper docs.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 66 lines · 87 tokens per session scan A 8fbc41f8c9a7
readme-blueprint-generator is a skill published in the GitHub repository appleweiping/WEIPING_WIKI (122 stars, last pushed 15d ago), licensed MIT. It adds 87 tokens to every session and 712 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.