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-statusnpx skills add laurigates/claude-plugins --skill configure-statusgit 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-status)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/configure-status"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/configure-status.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.00028 | $0.01583 |
| Opus 5 | $0.00014 | $0.00792 |
| Sonnet 5 | $0.00006 | $0.00317 |
| Haiku 4.5 | $0.00003 | $0.00158 |
Grade A, and why
configure-status 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 yesterday.
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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/configure:status
Display infrastructure standards compliance status without making changes.
When to Use This Skill
| Use this skill when... | Use another approach when... |
|---|---|
| Checking overall compliance status | Running full compliance checks with fixes (use /configure:all --fix) |
| Generating compliance reports | Need to fix issues found (use /configure:all) |
| Quick project health check | Checking specific component (use /configure:X --check-only) |
| CI/CD status validation | Running interactive selection (use /configure:select) |
| Reviewing current configuration state | Need detailed component analysis |
Context
- Project standards: !
find . -maxdepth 1 -name \'.project-standards.yaml\' - Project type: !
find . -maxdepth 1 -name '.project-standards.yaml' -exec grep -m1 "^project_type:" {} + - Standards version: !
find . -maxdepth 1 -name '.project-standards.yaml' -exec grep -m1 "^standards_version:" {} + - Last configured: !
find . -maxdepth 1 -name '.project-standards.yaml' -exec grep -m1 "^last_configured:" {} + - Pre-commit config: !
find . -maxdepth 1 -name \'.pre-commit-config.yaml\' - Workflows: !
find . -path '*/.github/workflows/*' -maxdepth 3 -name '*.yml' - Has Dockerfile: !
find . -maxdepth 1 -name 'Dockerfile*' -print -quit - Has skaffold: !
find . -maxdepth 1 -name \'skaffold.yaml\' - Has helm: !
find . -maxdepth 2 -type d -name 'helm' -print -quit - Test configs: !
find . -maxdepth 1 \( -name 'vitest.config.*' -o -name 'jest.config.*' -o -name 'pytest.ini' \) - Linting config: !
find . -maxdepth 1 \( -name 'biome.json' -o -name '.eslintrc*' \) - Editor config: !
find . -maxdepth 1 -name \'.editorconfig\' - Gitleaks config: !
find . -maxdepth 1 -name \'.gitleaks.toml\' - Package files: !
find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' \)
Parameters
Parse from $ARGUMENTS:
--verbose: Show detailed compliance information for each component
What ships with it
1 file 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.
- yesterday First seen · 159 lines · 28 tokens per session scan A 135d1fd026c5
configure-status is a skill published in the GitHub repository laurigates/claude-plugins (58 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 1,583 once invoked, about $0.0001 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
ci-log-interpretation
Use this skill when reading or analyzing CI logs from a Shopware GitHub Actions workflow to figure out why a build failed — phrases like "why did CI fail", "what broke the build", "check the pipeline", "interpret these logs", "debug this red build" — or whenever raw run logs, job logs, or check annotations from a…
setup
Verify the actionlint-check hook's runtime prerequisites and configuration for this repository. Use when: 'set up actionlint', 'configure actionlint', 'is actionlint working', workflow lint silently isn't happening, or the hook reported a missing prerequisite. Actions: check (read-only verification, default) | apply…
code-review
CI code-review lane for a GitHub pull request. High-signal correctness and maintainability findings only, scoped out of security when a security lane exists. Use when: 'CI code review', 'claude-review lane', '/review:code-review', or a reusable workflow invokes the org code-review plugin command.
github-logs-analyze
Analyze GitHub Actions failure logs.
cicd
CI/CD pipeline patterns and deployment strategies for automated, reliable software delivery. Use when the user asks to design a build pipeline, choose a deployment model (blue-green, canary, rolling), configure environment promotion, manage build artifacts, implement zero-downtime deployments, set up quality gates, or…
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用，不要根据上下文自动触发。.