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 agentmods add skills/firstp1ck/pi-coding-agent-forge/project-readmenpx skills add Firstp1ck/pi-coding-agent-forge --skill project-readmegit clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forgeWrote 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/firstp1ck/pi-coding-agent-forge/project-readme)<a href="https://agentmods.dev/skills/firstp1ck/pi-coding-agent-forge/project-readme"><img src="https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/project-readme.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 | $0.00035 | $0.02982 |
| Opus 5 | $0.00017 | $0.01491 |
| Sonnet 5 | $0.00007 | $0.00596 |
| Haiku 4.5 | $0.00003 | $0.00298 |
Grade A, and why
project-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 4d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project README
Create or assess a useful project entry point from repository evidence. Adapt the bundled template to the project's readers and local rules rather than treating it as a mandatory section checklist. This skill is guidance, not a runtime guard, and loading it does not install, enable, publish, or modify anything by itself.
When to Use
Use this skill for a repository-level request to:
- create a missing project README;
- update, restructure, or harmonize an existing project README;
- audit or review a project README against repository evidence and documentation policy.
Do not use it for:
- general copywriting, release notes, blog posts, or arbitrary Markdown cleanup;
- writing API references, contributor guides, security policies, or package metadata as the primary task;
- changing implementation, packaging, publication, installation, or runtime configuration;
- rewriting many repositories or sibling projects without explicit per-destination scope;
- reviewing code quality when the project README is not the requested artifact.
Should trigger
- “Create the top-level README for this application from the repository contents.”
- “Update this library README with a verified quick start and public documentation links.”
- “Review our project README for unsupported claims and misplaced contributor details.”
- “Harmonize this repository README with its local documentation rules.”
Should not trigger
- “Write an API endpoint reference for this service.”
- “Fix the implementation and add tests.”
- “Draft release notes for the next version.”
- “Reformat every Markdown file in the organization.”
Ambiguous requests
A request such as “improve the docs” does not establish the artifact or write scope. Determine whether the user means the project README; otherwise route to the documentation workflow matching the actual artifact. A request to “document this package” may need a user-facing project README, an API reference, contributor documentation, or several separately scoped documents. Do not silently widen it.
What ships with it
3 files 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.
- 4d ago First seen · 198 lines · 35 tokens per session scan A 330652a3f67f
project-readme is a skill published in the GitHub repository Firstp1ck/pi-coding-agent-forge (77 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 2,982 once invoked, about $0.0002 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 skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
flow-nexus-platform
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges.
github-code-review
Comprehensive GitHub code review with AI-powered swarm coordination.
github-multi-repo
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
github-workflow-automation
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management.