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 wahidyankf/ose-public --skill tooling-nxgit clone --depth 1 https://github.com/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/tooling-nx)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/tooling-nx"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/tooling-nx/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/wahidyankf/ose-public/tooling-nx"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/tooling-nx.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.00048 | $0.00800 |
| Opus 5.5 | $0.00019 | $0.00320 |
| Sonnet 5.5 | $0.00010 | $0.00160 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
tooling-nx 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 2d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nx Tooling
Every Nx rule is owned by Nx Standards, and every target rule by Task Runner Target Standards. The code inside each project follows that project's own language and framework skills. This skill adds only the procedure and judgement of working through the runner. Where a sentence here seems to state a rule, the standards decide.
Start From What the Project Records
Read the repository adapter for the tag vocabulary, the dependency constraints, and how boundaries outside JavaScript
and TypeScript are enforced. Read the project's README for its targets and every omitted one. Then ask Nx what it
resolved rather than reading configuration alone, for example nx show project <name>, because inferred targets and
workspace defaults never appear in the project file.
Select by the Project Graph, Not by Hand
Run change-scoped work through nx affected with the targets it needs. When a project you expected is missing from the
selection, that is the finding: look for the dependency or input Nx cannot see, declare it, and rerun. Listing the
project by hand makes this run pass and leaves the next one wrong. When one you did not expect appears, read the graph
before assuming Nx is wrong; an unexpected edge is often a real import.
Add a Target Only Where a Capability Exists
Before adding a target, confirm the project can really do what the name claims: a unit target runs unit tests that exist, and a coverage target measures something Meaningful Coverage admits. An inferred target the project cannot run is removed or excluded from inference, never left to pass on nothing. Record each omission in the project's README with its reason.
Cache Only Deterministic Targets
When a cached result is suspect, rerun the target with --skip-nx-cache. If the fresh run fails where the cached one
passed, the cache replayed a result its inputs did not determine. Find the missing input, usually a file another project
owns, an environment variable, or a tool version, add it to the target or a named input, and confirm the cache now
misses on that change. Turning caching off for the target hides the defect rather than fixing it, unless the target is
one the standard never caches.
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.
- 2d ago First seen · 64 lines · 48 tokens per session scan A 8e3bd2d76482
tooling-nx is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 800 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-14.
Other skills, from other repositories
turborepo
Configure and troubleshoot Turborepo repositories. Use when working with turbo.json, task pipelines, caching, Remote Cache, the turbo CLI, filtering, environment variables, package boundaries, monorepo structure, or CI workflows.
nx-plugin-for-aws
Scaffold and build cloud-native applications on AWS using @aws/nx-plugin generators. Use when the user wants to create workspaces, generate projects, or scaffold infrastructure with the Nx Plugin for AWS.
frontmcp-setup
Use when starting, scaffolding, or organizing a FrontMCP project. Covers creating a new project (CLI scaffold or manual) for Node, Vercel, and other targets; standalone versus Nx-monorepo layout, naming conventions, generators, and dependency rules; composing multiple @App classes, ESM packages, and remote MCP servers…
investigate-cloudflare
Investigate deployed Worker failures, regressions, and missing operational signals using Cloudflare Issues, logs, traces, SQL, or Observability MCP. Produce bounded evidence and verify recurrence against the deployed version.
add-a-lib
Scaffold a new shared library under libs/ in the builders-stack monorepo. Use when code is needed in two or more places (apps or services) and should become a single source of truth consumed by package name. Covers the package.json, tsconfig, the one-public-door src/index.ts barrel, and wiring it into a consumer…
implement
Implement an agreed issue or spec through implementation, review, fixes, and a PR ready to merge.