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/ohm41321/luciazero/readynpx skills add ohm41321/luciazero --skill readygit clone --depth 1 https://github.com/ohm41321/luciazeroWrote 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/ohm41321/luciazero/ready)<a href="https://agentmods.dev/skills/ohm41321/luciazero/ready"><img src="https://agentmods.dev/badge/skills/ohm41321/luciazero/ready.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.00050 | $0.01092 |
| Opus 5 | $0.00025 | $0.00546 |
| Sonnet 5 | $0.00010 | $0.00218 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade A, and why
ready 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 3d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ready
Leave the repository with one unattended command that returns a meaningful exit code, plus only the guardrails needed for future agents to self-verify. Detect the stack; do not assume it. Run every artifact you add.
1. Detect
Run the bundled scan first:
<this-skill-dir>/scripts/detect.sh <repo-root>
It finds candidates, not truth; open flagged files and interpret CI matrices or unusual build systems yourself. Inspect in this order:
- CI config: use what CI runs.
- Manifests and runners: package scripts, pyproject/tox/nox, Make/just, Cargo/go/Gradle/composer.
- README, CONTRIBUTING, CLAUDE.md, AGENTS.md, and docs; record docs/CI drift.
- Existing test directories and naming conventions.
Report run/test/lint/typecheck/build/git as command or MISSING. If this is not
a Git repository, propose git init but ask first.
2. Establish verification
Reuse the existing verify path. If none exists, create the smallest entrypoint in the repository's native convention.
The command must:
- exit non-zero on failure and run unattended;
- work offline without credentials, GPU, network, or secrets;
- use installed project tooling and avoid watch mode;
- stay quiet on success and be documented for humans.
Time it once. Use one tier when the suite is already quick. When slow checks would cripple the edit loop, define:
verify: lint/typecheck/unit or smoke coverage, normally under ~60 seconds;verify-full: integration/build/slow coverage, required at closeout and PR.
Run verify on every edit loop; run verify-full at closeout and before a PR.
For monorepos, prefer a repo-owned verify-changed backed by the workspace
dependency graph, with the root full suite as fallback. Read
references/smart-verification.md before
creating it and document its base revision and fallback.
For Claude Code enforcement-pack users, ask first before offering exact-match
tracking in the personal, gitignored .claude/settings.local.json:
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.
- 3d ago First seen · 126 lines · 50 tokens per session scan A c8c0a291fe04
ready is a skill published in the GitHub repository ohm41321/luciazero (5 stars, last pushed 10d ago), licensed MIT. It adds 50 tokens to every session and 1,092 once invoked, about $0.0003 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-31.
Other skills, from other repositories
neo4j-snowflake-graph-analytics-skill
Run Neo4j Graph Analytics algorithms (PageRank, Louvain, WCC, Dijkstra, KNN, Node2Vec, FastRP, GraphSAGE) directly inside Snowflake without moving data. Use when running graph algorithms against Snowflake tables via the Neo4j Snowflake Native App ("GDS Snowflake", "graph algorithms in Snowflake", "Neo4j Graph…
neo4j-agent-memory-skill
Authoritative reference for the neo4j-agent-memory Python package — a graph-native memory system for AI agents built on Neo4j — and for the hosted service (NAMS) at memory.neo4jlabs.com. Use this skill whenever the user mentions neo4j-agent-memory, agent memory with Neo4j, context graphs, the POLE+O model…
neo4j-cypher-skill
Generates, optimizes, and validates Cypher 25 queries for Neo4j 2025.x and 2026.x. Use when writing new Cypher queries, optimizing slow queries, graph pattern matching, vector or fulltext search, subqueries, or batch writes. Covers MATCH, MERGE, CREATE, WITH, RETURN, CALL, UNWIND, FOREACH, LOAD CSV, SEARCH…
neo4j-document-import-skill
Ingests unstructured and semi-structured documents into Neo4j as a knowledge graph. Use when chunking PDFs, HTML, plain text, or Markdown; extracting entities and relationships from text with an LLM (SimpleKGPipeline, neo4j-graphrag); loading JSON via apoc.load.json; building Document→Chunk→Entity graph structures; or…
neo4j-driver-dotnet-skill
Neo4j .NET Driver v6 — IDriver lifecycle, DI registration (singleton), ExecutableQuery fluent API, ExecuteReadAsync/ExecuteWriteAsync managed transactions, IResultCursor (FetchAsync/ ToListAsync), record value access (.Get /As ), null safety, UNWIND batching, temporal types, await using, EagerResult, object mapping…
neo4j-getting-started-skill
Orchestrates zero-to-running-app in 8 stages — prerequisites → context → provision → model → load → explore → query → build. Each stage reads its own reference file. Supports HITL and fully autonomous operation. Use when starting a new Neo4j project from scratch, provisioning Aura, generating synthetic data, building…