Borrowing it
Nothing to install: this file belongs to lglucas/ai-dev-operating-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lglucas/ai-dev-operating-system/main/.claude/skills/registry-pick/SKILL.mdgit clone --depth 1 https://github.com/lglucas/ai-dev-operating-systemWrote 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/lglucas/ai-dev-operating-system/registry-pick)<a href="https://agentmods.dev/skills/lglucas/ai-dev-operating-system/registry-pick"><img src="https://agentmods.dev/badge/skills/lglucas/ai-dev-operating-system/registry-pick.svg" alt="Measured on agentmods" 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.00098 | $0.01474 |
| Opus 5 | $0.00049 | $0.00737 |
| Sonnet 5 | $0.00020 | $0.00295 |
| Haiku 4.5 | $0.00010 | $0.00147 |
Grade A, and why
registry-pick 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Registry Pick
Read docs/registry/INDEX.md and docs/registry/packs/*.md, match the project's signals against pack tags and fit-signals, and produce a short, opinionated recommendation.
This skill does NOT install anything. It shortlists what is worth installing for THIS project.
When to invoke
The wizard invokes this skill twice, in two differently-scoped passes:
| Pass | WIZARD stage | Scope | Output |
|---|---|---|---|
| Design | 3.1 — before the Prototype Lab | Only design-oriented packs: UI systems, design tokens, component libraries, diagramming, screenshot/asset tooling | docs/technical/registry-pick-design.md |
| Stack | 4.3 — after the Technical Plan | The whole catalog | docs/technical/registry-pick.md |
The split is deliberate: design packs are worthless once the prototype is already built, and stack packs are guesswork before the Technical Plan exists.
Signals available differ between passes. In the design pass there is no Product Brief, no Technical Plan, and no prototype-lab/ yet — read BP v0.0.2 and knowledge-base/ instead, and do not ask for artifacts that Phase 3 has not produced.
Also invoke:
- When the user asks "que repos eu uso aqui?", "tem algum pack pra X?", "que skill externa ajuda nisso?".
- When a new domain need surfaces mid-build (compliance, design system, malware analysis, web3 integration).
- After adding a new pack to the registry, to retest the recommendation for the current project.
Inputs the skill needs
Before recommending, gather these from the project:
| Signal | Source | Example |
|---|---|---|
| Stack | package.json, Anchor.toml, requirements.txt, Gemfile, Cargo.toml |
@solana/web3.js → web3/Solana |
| Domain | docs/business/BUSINESS-PLAN.md, docs/product/PRODUCT-BRIEF.md (stack pass only) |
"PHI" → healthcare, "pagamentos" → fintech |
| Compliance | docs/technical/TECHNICAL-PLAN.md security/privacy section (stack pass only); BP v0.0.2 risk section in the design pass |
LGPD, GDPR, HIPAA, PCI |
| UI surface | BP v0.0.2 personas and positioning in the design pass; Product Brief + prototype-lab/ in the stack pass |
mobile, dashboard, B2C web |
| Public/private | repo metadata, deploy intent | public GitHub → enables gitleaks |
| Team familiarity | user statement | "primeira vez com Claude Code" → start with #foundations only |
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 · 138 lines · 98 tokens per session scan A 61a25e516efa
registry-pick is a skill published in the GitHub repository lglucas/ai-dev-operating-system (11 stars, last pushed 1mo ago), licensed MIT. It adds 98 tokens to every session and 1,474 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
phone-harness
Control the user's phone — iPhone through the Mac's iPhone Mirroring window, or an Android over adb: open apps, tap, type, swipe, read the screen.
security-audit
Java security checklist covering OWASP Top 10, input validation, injection prevention, and secure coding. Works with Spring, Quarkus, Jakarta EE, and plain Java. Use when reviewing code security, before releases, or when user asks about vulnerabilities.
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
architecture-review
Analyze Java project architecture at macro level - package structure, module boundaries, dependency direction, and layering. Use when user asks "review architecture", "check structure", "package organization", or when evaluating if a codebase follows clean architecture principles.
git-commit
Generate conventional commit messages for Java projects. Use when user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.