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.
npx agentmods add skills/laurigates/claude-plugins/configure-selectnpx skills add laurigates/claude-plugins --skill configure-selectgit clone --depth 1 https://github.com/laurigates/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/skills/laurigates/claude-plugins/configure-select)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/configure-select"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/configure-select.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 | $0.00038 | $0.01300 |
| Opus 5 | $0.00019 | $0.00650 |
| Sonnet 5 | $0.00008 | $0.00260 |
| Haiku 4.5 | $0.00004 | $0.00130 |
Grade A, and why
configure-select 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 today.
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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/configure:select
Interactively select which infrastructure standards checks to run.
When to Use This Skill
| Use this skill when... | Use another approach when... |
|---|---|
| Setting up selected components interactively | Running all components (use /configure:all) |
| Choosing specific standards to implement | Checking status only (use /configure:status) |
| Customizing configuration scope for project | Single component needed (use specific /configure:X skill) |
| User wants control over which components to configure | Automated full setup preferred |
| Building configuration incrementally | Complete infrastructure setup needed immediately |
Context
- Project standards: !
find . -maxdepth 1 -name \'.project-standards.yaml\' - Project type: !
find . -maxdepth 1 -name '.project-standards.yaml' -exec grep -m1 "^project_type:" {} + - Has terraform: !
find . -maxdepth 2 \( -name '*.tf' -o -type d -name 'terraform' \) -print -quit - Has package.json: !
find . -maxdepth 1 -name \'package.json\' - Has pyproject.toml: !
find . -maxdepth 1 -name \'pyproject.toml\' - Has Cargo.toml: !
find . -maxdepth 1 -name \'Cargo.toml\'
Parameters
Parse from $ARGUMENTS:
--check-only: Report status without offering fixes (CI/CD mode)--fix: Apply fixes automatically to all selected components
Execution
Execute this interactive component selection workflow:
Step 1: Detect project type
- Read
.project-standards.yamlif it exists (checkproject_typefield) - Auto-detect from file structure:
- infrastructure: Has
terraform/,helm/,argocd/, or*.tffiles - frontend: Has
package.jsonwith vue/react dependencies - python: Has
pyproject.tomlorrequirements.txt - rust: Has
Cargo.toml
- infrastructure: Has
- Report detected type to user
Step 2: List domains and components from the manifest
The component roster lives in the sibling manifest configure-all/components.yaml. Run the lister to get the current domains and their components:
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.
- today First seen · 142 lines · 38 tokens per session scan A 716bf994b81f
configure-select is a skill published in the GitHub repository laurigates/claude-plugins (57 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 1,300 once invoked, about $0.0002 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
prd
Produce a Product Requirements Document that locks product intent. Problem, users, success metrics. Before any engineering plan, with tiers (one-pager / consumer-feature / b2b-internal), a synthesize path, and a review mode. Use when: 'write a PRD', 'spec out a feature', 'product brief', 'product requirements doc'…
realign
Execute an instruction-placement audit's findings behind an explicit per-item human gate. Consumes the findings artifact the audit skill produced. It never re-judges the surface itself. For each finding the operator accepts, it performs the whole move atomically: create the path-scoped .claude/rules/ file with its…
morning-brief
Prints the operator's read-only morning view for the current GitHub repo in one pass. Open counts per queue label (needs-triage / ready / needs-decision / needs-human), the gh-native merge-ready PR list, parked decisions with their RECOMMENDED lines, and loop-lane telemetry freshness (last-cycle age + flags). Use…
wayfind
Chart a too-big, still-foggy effort as a shared decision map on the work-item tracker, then work its frontier one decision at a time, routing each resolved decision to the right skill until the map graduates to a Brief / PRD / PLAN. Use when a task is too big to hold at once AND parts are still too fuzzy to phrase as…
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
reuse-or-replace
Re-anchor the anti-fragmentation discipline that when an established way of doing something already exists, an idiom, structure, naming shape, doc format, or process, new work REUSES it or openly REPLACES it (migrate the old uses, record the decision); never a silent second, parallel way alongside. Then audit the work…