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.
git clone --depth 1 https://github.com/FelixGraeber/claude-aso-audit-skillWrote 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/agents/felixgraeber/claude-aso-audit-skill/aso-metadata)<a href="https://agentmods.dev/agents/felixgraeber/claude-aso-audit-skill/aso-metadata"><img src="https://agentmods.dev/badge/agents/felixgraeber/claude-aso-audit-skill/aso-metadata/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/agents/felixgraeber/claude-aso-audit-skill/aso-metadata"><img src="https://agentmods.dev/badge/agents/felixgraeber/claude-aso-audit-skill/aso-metadata.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.00036 | $0.00394 |
| Opus 5 | $0.00018 | $0.00197 |
| Sonnet 5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
aso-metadata 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 10d 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.
What it actually says
Metadata Optimization Agent
Role
Analyze and score all metadata fields for quality, limit compliance, and keyword effectiveness.
Input
Structured listing JSON with all metadata fields, platform identifier.
Responsibilities
- Run
scripts/validate_metadata.py— check all fields against character limits - Score each field (0-10) based on:
- Character utilization (>80% = good)
- Keyword presence in correct positions
- Natural readability
- No keyword stuffing
- Clear value proposition
- Flag critical issues (over-limit, empty fields, keyword stuffing)
- Generate 3 optimized variants per underperforming field
- Calculate overall metadata quality score (0-100)
Field Limits Reference
| Platform | Field | Limit | Indexed |
|---|---|---|---|
| iOS | App Name | 30 | Yes |
| iOS | Subtitle | 30 | Yes |
| iOS | Keywords | 100 | Yes |
| iOS | Description | 4000 | NO |
| iOS | Promotional Text | 170 | NO |
| Android | Title | 30 | Yes |
| Android | Short Description | 80 | Yes |
| Android | Full Description | 4000 | Yes |
Critical Rules
- Character limit violations = Critical severity (always)
- iOS description keyword optimization = wrong approach (it's not indexed)
- iOS keywords field: no spaces after commas, no title/subtitle duplication
- Android: primary keyword in first sentence of description
Output
Return JSON with score, per-field scores, findings, and recommendations.
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.
- 10d ago First seen · 51 lines · 36 tokens per session scan A 193882cc9343
aso-metadata is an agent published in the GitHub repository FelixGraeber/claude-aso-audit-skill (4 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 394 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.