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/attributes-collectnpx skills add laurigates/claude-plugins --skill attributes-collectgit 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/attributes-collect)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/attributes-collect"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/attributes-collect.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.00027 | $0.01116 |
| Opus 5 | $0.00014 | $0.00558 |
| Sonnet 5 | $0.00005 | $0.00223 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
attributes-collect 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/attributes:collect
Collect structured codebase health attributes with severity and remediation actions.
When to Use This Skill
| Use this skill when... | Use another approach when... |
|---|---|
| Need structured health assessment before routing | Quick health score only (use /health:check) |
| Want machine-readable attribute JSON | Human-readable report (use /attributes:dashboard) |
| Planning which agents to invoke | Already know what needs fixing |
| Comparing health across repos | Checking specific component only |
Parameters
| Parameter | Description |
|---|---|
--output <path> |
Write JSON to file (default: stdout) |
--categories <list> |
Comma-separated categories to check: docs,tests,security,quality,ci |
Execution
Perform these checks and output structured JSON.
Step 1: Documentation Attributes
Check for these files and emit attributes:
| Check | Attribute ID | Severity |
|---|---|---|
| README.md exists | missing-readme |
high |
| README.md > 200 chars | short-readme |
low |
| CLAUDE.md exists | missing-claude-md |
medium |
| docs/ directory exists | no-docs-directory |
low |
| LICENSE file exists | missing-license |
low |
Score: Start at 0, add points per check (max 20).
Step 2: Testing Attributes
| Check | Attribute ID | Severity |
|---|---|---|
| tests/ or test/ directory exists | no-test-directory |
high |
| Test config file exists (vitest, jest, pytest, etc.) | no-test-config |
medium |
| CI workflow runs tests | no-ci-tests |
high |
Test configs to look for: vitest.config.{ts,js}, jest.config.{js,ts}, pytest.ini, conftest.py, playwright.config.ts
Step 3: Security Attributes
| Check | Attribute ID | Severity |
|---|---|---|
| .gitignore exists | missing-gitignore |
high |
| .env file NOT committed | env-file-committed |
critical |
| Pre-commit hooks configured | no-pre-commit-hooks |
medium |
| Security scanning in CI | no-security-scanning |
high |
| Dependabot configured | no-dependabot |
low |
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 · 127 lines · 27 tokens per session scan A 7f32c847e87e
attributes-collect is a skill published in the GitHub repository laurigates/claude-plugins (57 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 1,116 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
feature-branch-pr-writing
Use this skill when the user asks to write, draft, create, or improve a PR description for a Shopware core repository PR — AND that PR targets a non-trunk feature branch (not trunk itself). Trigger phrases like "write a PR description", "draft the PR", "what should I put in the PR body". The skill detects the target…
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…
a0-create-plugin
Create, extend, or modify Agent Zero plugins. Follows strict full-stack conventions (usr/plugins, plugin.yaml, Store Gating, AgentContext, plugin settings). Use for UI hooks, API handlers, lifecycle extensions, or plugin settings UI.
a0-contribute-plugin
Guide for publishing an Agent Zero plugin to the community Plugin Index (a0-plugins repo). Covers GitHub repo setup, index.yaml creation, CI validation rules, and PR submission. Use when the user wants to share, publish, submit, or contribute a plugin to the Plugin Hub so other Agent Zero users can find and install it.
repo-activity
Scan all git repositories under /repos and report recent activity — last commit age, branch, uncommitted changes — in age-bucketed tables. Use when the user asks for a repo activity overview, "what have I been working on", portfolio status, or which repos are active/dormant.
a0-plugin-router
Main entry point for all Agent Zero plugin tasks. Routes to specialist skills for creating, reviewing, contributing, managing, or debugging plugins. Use when the user mentions plugins, asks how the plugin system works, wants to build/install/uninstall/publish/debug a plugin, or asks about the Plugin Hub.