working-in-monorepos

working-in-monorepos is a skill for Claude Code from technicalpickles/pickled-claude-plugins. It costs 44 tokens per session (2,012 once invoked), scanned A, original, MIT.

A workflow skill for repositories that contain several related projects in one codebase, known as a monorepo.

In plain words
What is it for?
Use it to run commands from the correct absolute paths while developing or testing projects in a monorepo.
Why use it?
It prevents commands from running in the wrong project directory when working across multiple subprojects.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/josh/workspace/schemaflow/ruby.

Part of the working-in-monorepos plugin — 1 skill, 1 command shipped together

Good fit Use it to run commands from the correct absolute paths while developing or testing projects in a monorepo.

Compare 6 skills from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add technicalpickles/pickled-claude-plugins
Claude Code
/plugin install working-in-monorepos

Made for: Claude Code.

Or install working-in-monorepos, the plugin that ships this one along with the rest of its 1 skill, 1 command.

Wrote 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.

agentmods badge for working-in-monorepos

README.md
[![agentmods](https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/working-in-monorepos/github.svg)](https://agentmods.dev/skills/technicalpickles/pickled-claude-plugins/working-in-monorepos)
Your own site
<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.

agentmods 80×15 button for working-in-monorepos

Your own site · 80×15
<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>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,012 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash 9b3c265274ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

plugins/working-in-monorepos/skills/working-in-monorepos/SKILL.md · 232 lines

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:

  1. Read root field for absolute repo path
  2. Read subproject path from subprojects map
  3. 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:

  1. First get the repo root: git rev-parse --show-toplevel
  2. 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

Read the full file on GitHub · 232 lines

Files

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.

Changes

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.

  1. 1mo ago First seen · 232 lines · 44 tokens per session scan A 9b3c265274ca

Subscribe to this mod's changes

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.

Related

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.

VidyFoo/antigravity-skill-engine · 27 tokens

release

A release-preparation workflow for software projects. It covers checks before publishing, version-number updates, changelog and documentation updates, and deployment checks.

u9401066/template-is-all-you-need · 60 tokens

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.

u9401066/template-is-all-you-need · 92 tokens

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.

smith-horn/product-builder-starter · 43 tokens

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.

Lion-1209/Lion-Skills · 15 tokens

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…

K-Dense-AI/scientific-agent-skills · 147 tokens