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 event4u-app/agent-config --skill monorepo-workspacegit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/monorepo-workspace)<a href="https://agentmods.dev/skills/event4u-app/agent-config/monorepo-workspace"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/monorepo-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/event4u-app/agent-config/monorepo-workspace"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/monorepo-workspace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 85 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 86 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 89 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.02003 |
| Opus 5 | $0.00023 | $0.01001 |
| Sonnet 5 | $0.00009 | $0.00401 |
| Haiku 4.5 | $0.00005 | $0.00200 |
Grade A, and why
monorepo-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 8d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monorepo workspace orientation
Read-only. Answers "what is this repository, structurally" before anything edits it: the package manager, the workspace list, the task runner, and the tasks the runner actually defines.
Every answer is a pointer plus a digest — the file that states the fact and
a short quotation of it — never a flattened claim. This is the Class-A shape
standards-from-config uses, and for the
same reason: a digest the reader can check beats a summary they have to trust.
When to use
- Before editing anything in a repository with
apps/,packages/,libs/, apnpm-workspace.yaml, aturbo.json, or annx.json. - "Which packages depend on
@org/ui?", "what doesbuildrun here?", "which workspace owns this file?" - Before a cross-workspace change, as the input to
blast-radius-analyzer§ Monorepo.
Not for authoring a component or picking a UI idiom — the stack detector
already reports the frontend workspace as state.stack.scope_root, and the UI
lane routes on that.
Procedure
1. Package manager — from the declaration, then the lockfile
packageManager in the root package.json is the declaration and wins when
present (it is what Corepack enforces). Otherwise infer from the lockfile:
pnpm-lock.yaml → pnpm, yarn.lock → yarn, bun.lock / bun.lockb → bun,
package-lock.json → npm. Two lockfiles is a finding, not a tie to break —
report both and stop.
2. Workspaces — from the declarative source
In precedence order, and report which one answered:
| Source | Field |
|---|---|
pnpm-workspace.yaml |
packages: |
package.json |
workspaces (array, or { packages: [...] }) |
nx.json beside per-project project.json |
Nx infers; use step 3 |
lerna.json |
packages |
Globs are globs: packages/* means every direct child carrying a manifest, not
every directory.
2b. Catalogs — the version is declared once, not per member
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.
- 8d ago First seen · 176 lines · 47 tokens per session scan A 9fcdfdfe767f
monorepo-workspace is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,003 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
contact-cache
Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.
pad
Talk to your project. Natural-language project management — create items, check status, plan work, brainstorm ideas, and more.
pm-arch
Skill "pm-arch" from wei63w/pm-manager, covering user input, outline, done when and shared workflow (all /pm- commands).
pm-discover
Skill "pm-discover" from wei63w/pm-manager, covering user input, outline and shared workflow.