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.
git clone --depth 1 https://github.com/technicalpickles/pickled-claude-pluginsWrote 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/plugins/technicalpickles/pickled-claude-plugins/working-in-monorepos)<a href="https://agentmods.dev/plugins/technicalpickles/pickled-claude-plugins/working-in-monorepos"><img src="https://agentmods.dev/badge/plugins/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/plugins/technicalpickles/pickled-claude-plugins/working-in-monorepos"><img src="https://agentmods.dev/badge/plugins/technicalpickles/pickled-claude-plugins/working-in-monorepos.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
This is a copy
86% identical to ci-cd-tools — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"name": "working-in-monorepos",
"description": "Navigate and execute commands in monorepo subprojects",
"author": {
"name": "Josh Nichols",
"email": "[email protected]"
},
"repository": "https://github.com/technicalpickles/pickled-claude-plugins",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill, 1 command travel with it, and installing the plugin installs all of them — 62 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 11 lines scan A 0fdf20a79fde
working-in-monorepos is a plugin published in the GitHub repository technicalpickles/pickled-claude-plugins (11 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. It is 86% identical to ci-cd-tools, differing in 4 lines, and is treated as a copy.
Other plugins, from other repositories
han-github
Github specific extensions to the Han plugin for agentic planning and coding. Provides skills to post code reviews as PR comments, update a PR description with a consistent format, etc.
dark-factory
Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the platform's getissue tool, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implemen.
git-tools
Git workflow skills — worktrees for parallel, conflict-free work on multiple branches.
spring-clean
Two passes over a repo. spring-clean measures against a declared scoreboard, deletes or gitignores what does not belong, relocates dev docs, notes, clones and dumps to a -workspace repo, splits oversized files, draws package boundaries and writes its plan to a numbered unit list that survives a dead context. w.
fork-and-pr
Guide contributors through a GitHub fork and one pull request to an upstream repository.
branch-recap
Tells you what your branch actually changed — what was done, why, and what deserves a second look, instead of the diff — then files the fixes into the commits they belong to.