Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nguyenthienthanh/aura-frognpx agentmods add skills/nguyenthienthanh/aura-frog/monorepoWrote 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/nguyenthienthanh/aura-frog/monorepo)<a href="https://agentmods.dev/skills/nguyenthienthanh/aura-frog/monorepo"><img src="https://agentmods.dev/badge/skills/nguyenthienthanh/aura-frog/monorepo/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/nguyenthienthanh/aura-frog/monorepo"><img src="https://agentmods.dev/badge/skills/nguyenthienthanh/aura-frog/monorepo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 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 Agent Snooping · line 113 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 114 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00060 | $0.01155 |
| Opus 5 | $0.00030 | $0.00577 |
| Sonnet 5 | $0.00012 | $0.00231 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
monorepo 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 9d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-consumed reference. Optimized for Claude to read during execution. Human-readable explanation: see docs/architecture/HIERARCHICAL_PLANNING.md or docs/getting-started/ depending on topic.
Monorepo Handling
Monorepos break many assumptions: which package.json is "the" one, where node_modules live, which test command runs, what install actually does. This skill ensures operations target the correct scope.
Detection
On session start or first file edit, check for these markers:
| File | Tool |
|---|---|
pnpm-workspace.yaml |
pnpm workspaces |
turbo.json |
Turborepo |
nx.json |
Nx |
lerna.json |
Lerna |
package.json with "workspaces": [...] |
npm / yarn workspaces |
Cargo.toml with [workspace] |
Rust workspaces |
go.work |
Go workspaces |
pyproject.toml with Poetry/uv workspace config |
Python workspaces |
If detected → monorepo mode ON. Record in workflow state. All subsequent commands must respect package scope.
Key Rules
1. Always identify the target package first
Before any install, test, or build:
- Which package is the change in? Full path:
packages/<name>/ - Run scoped, not from root:
pnpm --filter <name> test
2. Cross-package changes = coordinate
If a change touches package A's API used by package B:
- List all consumers:
grep -r "@your-org/package-a" packages/ - Update all consumers in the same PR
- Run tests across all affected packages, not just A
3. Dependency placement matters
| Dependency type | Where to install |
|---|---|
| Used by 1 package | That package's package.json |
| Used by 2+ packages | Shared config package or root devDependencies |
| Dev tooling (eslint, prettier, jest) | Root |
| Workspace packages | Listed as "workspace:*" in consumer's dependencies |
4. Build order respects the dependency graph
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.
- 9d ago First seen · 117 lines · 60 tokens per session scan A fd3229f604b4
monorepo is a skill published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed 8d ago), licensed MIT. It adds 60 tokens to every session and 1,155 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-09-03.
Other skills, from other repositories
review-pr
Multi-agent PR review with four modes (review, re-review, self-review, address-feedback) - spawns parallel subagents, saves diff to /tmp for context efficiency, supports file exclusion patterns.
feature
Deliver a feature or chore end to end, from branch creation to PR readiness, starting from an issue URL or a plain description.
commit
Create git commits with user approval and no Claude attribution.
github-commander
Structured workflows for GitHub issues, PRs, milestones, and code audits with validation gates and HITL checkpoints. Use when assigned a GitHub issue, reviewing a PR, sprinting through a milestone, updating dependencies, or running code audits. Also use when asked to "triage an issue", "review a PR", or "update deps".…
gitlab
Specialized assistant skill for managing repositories and CI/CD in GitLab. Activate when the user asks about GitLab projects or repositories, wants to see merge requests or pipelines, needs to search code or files, asks about CI/CD status or job logs, or wants to browse repository contents. Mentions "GitLab", "glab"…
anchor.maintain
An internal maintenance workflow for the Anchorlaw protocol, a language-independent set of rules and implementations. It requires tests, self-checking, evidence in protocol documents, and disciplined versioning and commits.