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/monkilabs/opencastle/strapinpx skills add monkilabs/opencastle --skill strapigit clone --depth 1 https://github.com/monkilabs/opencastleWhat 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.00623 |
| Opus 5 | $0.00025 | $0.00311 |
| Sonnet 5 | $0.00010 | $0.00125 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
strapi-cms 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strapi CMS
Project config, content types, and deployment details: cms-config.md. Docs: https://docs.strapi.io/
File placement is load-bearing
Strapi discovers code by path — a correct file in the wrong place is simply ignored.
src/api/<type>/content-types/<type>/schema.json— content type (or use Content-Type Builder, then commit the generated schema)src/api/<type>/controllers/<type>.js— thin wrapper, wrapscreateCoreController('api::<type>.<type>', ({ strapi }) => ({ ... })); callsuper.find(ctx)then modify the responsesrc/api/<type>/services/— all business logicsrc/api/<type>/content-types/<type>/lifecycles.js—beforeCreate/afterUpdateside effects, mutatingevent.params.datasrc/api/<type>/graphql/— custom resolversconfig/env/<env>/— per-environment config;config/plugins.tsregisters plugins
Query gotchas
- Relations are not returned unless requested.
?populate=author,categories, or?populate=deepfor everything. - Filters need an operator:
?filters[status][$eq]=published&filters[views][$gte]=100. Operators include$eq,$contains,$in,$gte. - Field selection is indexed:
?fields[0]=title&fields[1]=slug. - Pagination:
?pagination[page]=1&pagination[pageSize]=10. - New endpoints return 403 until permissions are granted per role in Users & Permissions — this is the most common "my API is broken" cause.
- GraphQL is opt-in via
@strapi/plugin-graphql; it auto-generates types and resolvers from content types withfilters/pagination/sortargs. - Plugins:
strapi generate plugin <name>→admin/,server/,content-types/. Keep server logic inserver/so admin code is not bundled into the server build.
Verify
the develop script, confirm the type appears in admin, create a test entry, then assert GET /api/<type>?pagination[page]=1 returns 200 with a data array and GET /api/<type>?populate=* returns the expected relations. Schema errors surface under the build script.
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.
- 3d ago First seen · 36 lines · 50 tokens per session scan A e89050f4d628
strapi-cms is a skill published in the GitHub repository monkilabs/opencastle (61 stars, last pushed 5d ago), licensed MIT. It adds 50 tokens to every session and 623 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-30.
Other skills, from other repositories
product-architect
Complete product development system with 64 agents and 35 frameworks. Use when the user wants to build a product, write a PRD, plan an MVP or roadmap, design an app, research a market or check whether a feature already exists or is novel, do competitive analysis, run a security audit, build a financial model, plan…
codex-delegation
Use when a coding task would benefit from delegating work to Codex in the background — a deep independent second opinion, security or architecture analysis, or a parallel implementation running while the session continues. Lets Claude drive the codex companion itself (task, review, status --wait, result) without the…
cursor-delegation
Use when a coding task would benefit from delegating work to Cursor in the background — fast parallel implementation, scaffolding, or an everyday review running while the session continues. Lets Claude drive the cursor companion itself (task, review, status --wait, result) without the user typing /cursor: commands.
cursor-cli-runtime
Internal helper contract for calling the cursor-companion runtime from Claude Code.
cursor-prompting
Internal guidance for composing cursor-agent prompts and picking models for coding, review, diagnosis, and research tasks inside the Cursor Claude Code plugin.
goal-runner
Use when the user asks to advance, continue, or work on the project's long-horizon goal (or to set one up) — the policy for goal-driven increments driven through the goal companion, one increment at a time, delegated via the codex/cursor delegation skills, honestly recorded.