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/chachamaru127/codex-harness/crudnpx skills add Chachamaru127/codex-harness --skill crudgit clone --depth 1 https://github.com/Chachamaru127/codex-harnessWrote 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/chachamaru127/codex-harness/crud)<a href="https://agentmods.dev/skills/chachamaru127/codex-harness/crud"><img src="https://agentmods.dev/badge/skills/chachamaru127/codex-harness/crud.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.00057 | $0.00816 |
| Opus 5 | $0.00028 | $0.00408 |
| Sonnet 5 | $0.00011 | $0.00163 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
crud 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRUD Skill
Auto-generates CRUD functionality for specified entities (tables) at production-ready level.
Quick Reference
- "Create CRUD for task management" →
/crud tasks - "Want search and pagination too" → Includes all together
- "Include permissions (who can view/edit)" → Sets up authorization/rules together
Deliverables
- CRUD + validation + authorization + tests, complete production-safe set
- Minimize diff to match existing DB/code
Features:
- Validation (Zod) auto-add
- Auth/authorization (Row Level Security) auto-config
- Relations (one-to-many, many-to-many) support
- Pagination, search, filters
- Auto-generated test cases
Auto-invoke Skills
This skill must explicitly invoke the following skills with the Skill tool:
| Skill | Purpose | When to Call |
|---|---|---|
impl |
Implementation (parent skill) | CRUD feature implementation |
verify |
Verification (parent skill) | Post-implementation verification |
Execution Flow
Detailed steps are described in the phases below.
Phase 1: Entity Analysis
- Parse entity name from $ARGUMENTS
- Detect existing schema (Prisma, Drizzle, raw SQL)
- Infer field types and relations
Phase 2: CRUD Generation
- Generate model/schema if needed
- Create API endpoints (REST or tRPC)
- Add validation schemas (Zod)
- Configure authorization rules
Phase 3: Test Generation
- Create unit tests for each endpoint
- Add integration tests
- Generate test fixtures
Phase 4: Verification
- Run type check
- Run tests
- Verify build
Supported Frameworks
| Framework | Detection | Generated Files |
|---|---|---|
| Next.js + Prisma | prisma/schema.prisma |
API routes, Prisma client |
| Next.js + Drizzle | drizzle.config.ts |
API routes, Drizzle queries |
| Express | express in package.json |
Controllers, routes |
| Hono | hono in package.json |
Route handlers |
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.
- 4d ago First seen · 110 lines · 57 tokens per session scan A c34c6c81f480
crud is a skill published in the GitHub repository Chachamaru127/codex-harness (2 stars, last pushed 6mo ago), licensed MIT. It adds 57 tokens to every session and 816 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…