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 skills add rossumai/claude-marketplace --skill evaluate-namingsgit clone --depth 1 https://github.com/rossumai/claude-marketplaceWrote 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/rossumai/claude-marketplace/evaluate-namings)<a href="https://agentmods.dev/skills/rossumai/claude-marketplace/evaluate-namings"><img src="https://agentmods.dev/badge/skills/rossumai/claude-marketplace/evaluate-namings/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/skills/rossumai/claude-marketplace/evaluate-namings"><img src="https://agentmods.dev/badge/skills/rossumai/claude-marketplace/evaluate-namings.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.02331 |
| Opus 5.5 | $0.00014 | $0.00932 |
| Sonnet 5.5 | $0.00007 | $0.00466 |
| Haiku 4.5 | $0.00003 | $0.00233 |
Grade A, and why
evaluate-namings 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 2mo 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evaluate Namings
Overview
Audit naming conventions for a Rossum prd project. Profile the project first to establish context, then evaluate workspaces, queues, hooks, schema fields, and MDH datasets against their rules.
Step 1: Profile the Project
Read prd_config.yaml. Derive and output:
| Dimension | How to determine |
|---|---|
| Size | Count active use cases: small (1–2 workspaces, <5 queues/workspace), medium (3–4 workspaces), large (5+ workspaces) |
| Deployment type | Multiple distinct api_base values → multiple organisations; single api_base → single organisation |
| Environments | Subdirectory names under each directory in prd_config.yaml — this is the ground truth |
| Use cases | Union of active workspaces across all orgs (deduplicated). Exclude workspaces whose names contain: training, train, archive, archival. Not all use cases need to be in all orgs. |
Output the profile before continuing.
Step 2: Workspaces
Format: ({abbreviation}) {workspace name} {environment}
- All parts optional; order is fixed
- Abbreviation in
(), always first - Environment always last; only present for single-org deployments
- Environment bracket style flexible:
DEV,(DEV),[DEV]
| Issue | Bad | Good |
|---|---|---|
| Environment not last | DEV Invoices (Italy) |
Invoices IT (DEV) |
| Abbreviation not in parentheses | IT Invoices (DEV) |
(IT) Invoices (DEV) |
| Environment present in multi-org | Acosta [PROD] |
Acosta |
Step 3: Queues
Format: {number} ({use case}) {queue name}
- All parts optional; order is fixed
- Number prefix optional, may be followed by
._or similar separator - Use case in
()— mandatory when multiple sub-use-cases share a workspace - No environment tags — environment belongs at workspace level
- Queue name: concise; use abbreviations, not verbose descriptions
| Issue | Bad | Good |
|---|---|---|
| Environment tag in queue name | PO-backed invoices (TEST) |
PO-backed |
| Verbose description | Inbox for Invoices Germany |
(DE) Inbox |
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.
- 2mo ago First seen · 203 lines · 34 tokens per session scan A 9c78926efd81
evaluate-namings is a skill published in the GitHub repository rossumai/claude-marketplace (5 stars, last pushed 5d ago), licensed MIT. It adds 34 tokens to every session and 2,331 once invoked, about $0.0001 per session on Opus 5.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-31.
evaluate-namings compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| evaluate-namingsrossumai/claude-marketplace | Skill | 5 | 5d ago | MIT | A | 34 | Claude Code |
| imagegenopenai/codex | Skill | 135k | today | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 100k | today | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 316k | 8d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |