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 rodolfochicone/rc-project --skill rc-readmegit clone --depth 1 https://github.com/rodolfochicone/rc-projectWrote 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/rodolfochicone/rc-project/rc-readme)<a href="https://agentmods.dev/skills/rodolfochicone/rc-project/rc-readme"><img src="https://agentmods.dev/badge/skills/rodolfochicone/rc-project/rc-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/skills/rodolfochicone/rc-project/rc-readme"><img src="https://agentmods.dev/badge/skills/rodolfochicone/rc-project/rc-readme.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.00036 | $0.01917 |
| Opus 5 | $0.00018 | $0.00958 |
| Sonnet 5 | $0.00007 | $0.00383 |
| Haiku 4.5 | $0.00004 | $0.00192 |
Grade A, and why
rc-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 9d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
README
Produce a README.md that reflects what the code actually does — never invented or aspirational content. Every claim must trace back to a file you read. This skill is standalone and stack-agnostic; it detects the project's technology before writing.
Required Inputs
- None. Operates on the current repository root.
- Optional: a target path other than
README.md, or specific sections to scope the update to.
Workflow
-
Gather documentation context.
- Read, when present: the existing
README.md,CLAUDE.md,AGENTS.md,CONTRIBUTING.md, anydocs/overview, and architecture notes or ADRs underdocs/,.techdocs/, or.rc/tasks/*/adrs/(in monorepos there may be more than one.rcdirectory — scan each one, skippingnode_modules,.git,vendor, and_archived/). - The existing README defines the structure and tone to preserve. Keep valid sections; only rewrite what is stale.
- Read, when present: the existing
-
Detect the stack and analyze the codebase. Read real sources — do not guess.
- Manifest and stack: inspect
go.mod,package.json,pyproject.toml,Cargo.toml,pom.xml,*.csproj,Gemfile, etc. Record real dependency versions, the language, frameworks, and the package/registry. - Entry points and public API: the binary
main, exported packages, library entry, or CLI commands. - HTTP / RPC surface: route definitions, handlers, controllers, or service files. Capture method, path, and the request/response contract from the validation layer (schemas, DTOs, structs).
- Configuration: environment variables and config files — which are required vs optional, and defaults.
- Scripts and tasks: real commands from
package.jsonscripts,Makefile,Taskfile,justfile, etc. - Persistence: migrations or schema files — tables/collections and their shape.
- CI/CD: workflows under
.github/workflows/or equivalent — triggers and deploy targets. - Project structure: map the real directory tree (Glob), describing each significant directory's purpose.
- For an unfamiliar framework, spawn an Agent to map the relevant files rather than guessing conventions.
- Manifest and stack: inspect
What ships with it
5 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.
- 9d ago First seen · 134 lines · 36 tokens per session scan A 8c6f222e0f3e
rc-readme is a skill published in the GitHub repository rodolfochicone/rc-project (19 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,917 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
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
security-audit
Audit a codebase or directory for security issues (hardcoded secrets, injection, unsafe deserialization, weak crypto, authz gaps) and produce a structured findings report. Use when the user asks for a security review, an audit, or to check code for vulnerabilities. Report only — never fix.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
taiyi-diagram-c4
A code-scanning tool that builds C4 architecture documents from a repository. It separates facts observed in the code from conclusions inferred about the design and uses Mermaid diagrams as the source format.