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 monkilabs/opencastle --skill nx-workspacegit clone --depth 1 https://github.com/monkilabs/opencastleWrote 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/monkilabs/opencastle/nx-workspace)<a href="https://agentmods.dev/skills/monkilabs/opencastle/nx-workspace"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/nx-workspace/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/monkilabs/opencastle/nx-workspace"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/nx-workspace.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.00047 | $0.00628 |
| Opus 5.5 | $0.00019 | $0.00251 |
| Sonnet 5.5 | $0.00009 | $0.00126 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
nx-workspace 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 20d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NX Workspace
Docs: https://nx.dev/getting-started/intro. Project name → location mapping: .opencastle/project.instructions.md.
Never bypass NX
# FORBIDDEN — skips caching, parallelism, and dependency resolution:
npm test | npm run test | npm run lint | npm run build | npm run dev | npm start
npx jest | npx eslint | jest --coverage | eslint --fix
Always npx nx run <project>:<target> for one project, npx nx affected -t <target> for multi-project changes.
Requirements
- Coverage must meet the threshold in the project's test config; reports land in the path that config sets.
- Lint always with
--fix. CSS/SCSS uses a separate target:npx nx run <project>:lint-styles --fix. npx nx run <project>:test -uupdates snapshots.npx nx format --fixafter any generation.
MCP tools — query, don't guess
| Tool | When |
|---|---|
nx_workspace |
First call — architecture and current errors |
nx_docs |
Any config question; check before assuming |
nx_project_details |
One project's targets, config, dependencies |
nx_visualize_graph |
Project/task dependency graph |
nx_generators |
List generators (plugin + local) |
nx_generator_schema |
Required options and defaults for one generator |
nx_available_plugins |
Only when no existing generator fits |
nx_current_running_tasks_details |
Running/completed/failed tasks |
nx_current_running_task_output |
Terminal output for one task |
Generation
Prefer local generators over plugin generators — they encode repo conventions. Manual file creation is a last resort after nx_generators and nx_available_plugins both come up empty. Read nx_generator_schema, then read the generator source for side effects (config edits, dep installs).
npx nx generate <generator> <options> --dry-run --no-interactive # preview
npx nx generate <generator> <options> --no-interactive
--no-interactiveis mandatory — prompts hang the run with no output.- Verify cwd first — generators derive file placement from it.
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.
- 20d ago Changed · -2 lines · +1 tokens per session 93897e9a4768
- 21d ago First seen · 59 lines · 46 tokens per session scan A 58fe958f1fd9
nx-workspace is a skill published in the GitHub repository monkilabs/opencastle (80 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 628 once invoked, about $0.0002 per session on Opus 5.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-10-04.
Other skills, from other repositories
jira-ticket-builder
Turns rough input into structured Jira work. Two modes — single-ticket mode turns a bug description, meeting notes, Slack thread, incident writeup, or a few sentences into one fully-structured Jira ticket; decomposition mode turns a rough requirements doc or product brief with multiple asks and open questions into…
task-forest
Maintains a repo-local task forest or task DAG for the current workspace. Use when the user asks to initialize or update a task forest, close a session, summarize evolving project work, align a request with a global goal, track progress/history/deviations/todos, save or apply a task proposal, or export the…
work-report-expert
A writing guide for workplace summaries and presentations, including annual reviews, performance reports, project updates, job-promotion speeches, weekly reports, and monthly reports. It uses clear conclusions, evidence, and the STAR method, which explains a Situation, Task, Action, and Result.
workflow-discovery
Rank workflow candidates using observed repositories, skills, engineering activity and recurring user requests.
product-architect
Complete product development system with 80 agents and 36 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…
orchardcore-crestapps-recipes
Skill for the CrestApps Recipes module in Orchard Core, which publishes JSON Schema for recipe steps. Covers RecipeSchemaService, RecipeExecutionService, the schema-aware JSON Import editor, custom IRecipeStep providers, Settings step contributions, content definition and content item schemas, the composed Layers…