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 GiustoPiedimonte/agentic-engineering-marketplace --skill readmegit clone --depth 1 https://github.com/GiustoPiedimonte/agentic-engineering-marketplaceWrote 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/giustopiedimonte/agentic-engineering-marketplace/readme)<a href="https://agentmods.dev/skills/giustopiedimonte/agentic-engineering-marketplace/readme"><img src="https://agentmods.dev/badge/skills/giustopiedimonte/agentic-engineering-marketplace/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/giustopiedimonte/agentic-engineering-marketplace/readme"><img src="https://agentmods.dev/badge/skills/giustopiedimonte/agentic-engineering-marketplace/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.00132 | $0.02464 |
| Opus 5 | $0.00066 | $0.01232 |
| Sonnet 5 | $0.00026 | $0.00493 |
| Haiku 4.5 | $0.00013 | $0.00246 |
Grade A, and why
readme scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
style/structure, accessibility, freshness. Use the portable `git`/`curl`/`grep` How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/readme — audit & elevate a public README
A README is a contract: every claim — version, install command, link, badge — is implicitly promised true. This skill keeps that contract honest and raises the README to a high standard.
$ARGUMENTS is an optional path plus either a mode keyword or a free-form goal.
With no path, discover and handle every README in the repo, not just the root
one. Match files whose basename is
README.md (or README.<lang>.md for translations) — not a substring match, which
would wrongly pull in reference docs like README_CHECKLIST.md:
git ls-files | grep -E '(^|/)README(\.[a-z]{2})?\.md$'
This finds the root README plus nested ones (plugins/*/README.md,
packages/*/README.md, docs/**/README.md, …). Apply the right tier to each
(see below); don't impose the landing-page look on a component reference. Pass a
path to target a single file.
Modes — a keyword, or a free-form goal:
- A free-form intent (e.g. "add a quickstart", "make the hero punchier", "just the banner", "add an FAQ") — do only that, at minimal scope. Mention adjacent issues you notice; don't touch them without a fresh ok. This is the default when a goal is given without a keyword — collaborate on the intent, don't audit-everything or rebuild-everything.
audit— report only: ranked pass/fail findings, no edits.elevate(default for a thin/generic/empty README) — rebuild it to a polished, project-faithful README (see the fidelity gate): a fitting hero, honest badges, an adaptive element set, funnel structure, real examples.fix— apply the audit's fixes to an already-good README without a full rebuild.
The governing rule across all modes is the honesty gate: never show a signal you cannot back. No CI badge without a workflow, no version badge a release will outdate, no registry badge without a published package, no "used by" without real users, no vanity chip without a link to its proof. A broken or dishonest badge is worse than none — when in doubt, drop it.
What ships with it
2 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.
- 10d ago First seen · 176 lines · 132 tokens per session scan A 203e90d5a37e
readme is a skill published in the GitHub repository GiustoPiedimonte/agentic-engineering-marketplace (13 stars, last pushed 1mo ago), licensed MIT. It adds 132 tokens to every session and 2,464 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
grill-me
Internal requirements-interview engine for the CCF commands plan and init. Invoked only by those commands through the Skill tool with a mode argument (plan / init); it interrogates the user one question at a time, exploring the code to self-answer first, and returns a summary of the decisions. Not a standalone…
adr-new
Create a new Architecture Decision Record with append-only, status-gated supersession, and update the ADR index. Invoke with /adr-new, or let /tdd-author invoke it on approval of an ADR action (this skill stays model-invocable for that reason).
cco-tools
Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses.
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
test-run
Run plugin test suites in this monorepo and report a concise pass/fail summary. Optional plugin slug arg; without arg, runs all plugins under plugins/.
design-system-reference
Style guides and implementation rules for frontend design. Works with design-discovery agent which handles context gathering and VS-based style recommendations. Contains detailed style guides, anti-patterns, and implementation checklists.