Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add technicalpickles/pickled-claude-plugins/plugin install working-in-monoreposWrote 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/technicalpickles/pickled-claude-plugins/working-in-monorepos)<a href="https://agentmods.dev/skills/technicalpickles/pickled-claude-plugins/working-in-monorepos"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/working-in-monorepos/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/technicalpickles/pickled-claude-plugins/working-in-monorepos"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/working-in-monorepos.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.00044 | $0.02012 |
| Opus 5.5 | $0.00018 | $0.00805 |
| Sonnet 5.5 | $0.00009 | $0.00402 |
| Haiku 4.5 | $0.00004 | $0.00201 |
Grade A, and why
working-in-monorepos 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 1mo 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working in Monorepos
Overview
Helps Claude work effectively in monorepo environments by ensuring commands always execute from the correct location using absolute paths.
Core principle: Bash shell state is not guaranteed between commands. Always use absolute paths.
Announce at start: "I'm using the working-in-monorepos skill."
When to Use
Use this skill when:
- Repository contains multiple subprojects (ruby/, cli/, components/*, etc.)
- Commands must run from specific directories
- Working across multiple subprojects in one session
Don't use for:
- Single-project repositories
- Repositories where all commands run from root
The Iron Rule: Always Use Absolute Paths
When executing ANY command in a monorepo subproject:
✅ CORRECT:
cd /Users/josh/workspace/schemaflow/ruby && bundle exec rspec
cd /Users/josh/workspace/schemaflow/cli && npm test
❌ WRONG:
# Relative paths (assumes current directory)
cd ruby && bundle exec rspec
# No cd prefix (assumes location)
bundle exec rspec
# Chaining cd (compounds errors)
cd ruby && cd ruby && rspec
Why: You cannot rely on shell state. Absolute paths guarantee correct execution location regardless of where the shell currently is.
Constructing Absolute Paths
With .monorepo.json Config
If .monorepo.json exists at repo root:
- Read
rootfield for absolute repo path - Read subproject
pathfromsubprojectsmap - Construct:
cd {root}/{path} && command
Example:
{
"root": "/Users/josh/workspace/schemaflow",
"subprojects": { "ruby": { "path": "ruby" } }
}
→ cd /Users/josh/workspace/schemaflow/ruby && bundle exec rspec
Without Config
Use git to find repo root, then construct absolute path:
- First get the repo root:
git rev-parse --show-toplevel - Use that absolute path:
cd /absolute/path/to/repo/ruby && bundle exec rspec
Example workflow:
# Step 1: Get repo root
git rev-parse --show-toplevel
# Output: /Users/josh/workspace/schemaflow
# Step 2: Use absolute path in commands
cd /Users/josh/workspace/schemaflow/ruby && bundle exec rspec
What ships with it
6 files 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.
- 1mo ago First seen · 232 lines · 44 tokens per session scan A 9b3c265274ca
working-in-monorepos is a skill published in the GitHub repository technicalpickles/pickled-claude-plugins (11 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 2,012 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-09-03.
Other skills, from other repositories
ecosystem-managing
A codebase maintenance guide covering releases, cleanup, and project handoffs. A release means publishing a new software version; a handoff is documentation that helps another developer take over the project.
release
A release-preparation workflow for software projects. It covers checks before publishing, version-number updates, changelog and documentation updates, and deployment checks.
git-precommit
A pre-commit workflow that coordinates updates to project memory, documentation, changelogs, roadmaps, architecture notes, and commit messages before code is saved to Git.
Worktree Manager
Manage git worktrees for parallel development with conflict prevention and wave-aware execution strategy. Use when creating feature branches, starting parallel work sessions, merging worktree PRs, or coordinating multiple Claude sessions.
commit-message
A guide for writing clear, traceable Git commit messages using the Conventional Commits format, which labels changes such as features, bug fixes, documentation, and refactoring.
datalad
Retrieves, versions, and publishes scientific datasets with DataLad and git-annex, and captures computational provenance with datalad run, rerun, and containers-run. Use when cloning or fetching data from OpenNeuro, DANDI, datasets.datalad.org, or any DataLad dataset; when a file in a dataset reads as a broken symlink…