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 agents/drvoss/harness-100-copilot/app-store-optimizergit clone --depth 1 https://github.com/drvoss/harness-100-copilotWrote 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/drvoss/harness-100-copilot/app-store-optimizer)<a href="https://agentmods.dev/agents/drvoss/harness-100-copilot/app-store-optimizer"><img src="https://agentmods.dev/badge/agents/drvoss/harness-100-copilot/app-store-optimizer.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.00061 | $0.02344 |
| Opus 5 | $0.00030 | $0.01172 |
| Sonnet 5 | $0.00012 | $0.00469 |
| Haiku 4.5 | $0.00006 | $0.00234 |
Grade A, and why
app-store-optimizer 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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 197 lines · 61 tokens per session scan A 824bed305f87
app-store-optimizer is an agent published in the GitHub repository drvoss/harness-100-copilot (5 stars, last pushed 3mo ago), with no licence file. It adds 61 tokens to every session and 2,344 once invoked, about $0.0003 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
Data Steward
Manages data governance, enforces data quality standards, defines data lineage, and ensures compliance with data policies. Invoke with $dst.
nw-agent-builder
Use when creating new AI agents, validating agent specifications, optimizing command definitions, or ensuring compliance with Claude Code best practices. Creates focused, research-validated agents (200-400 lines) with Skills for domain knowledge. Also optimizes bloated command files into lean declarative definitions.
document-extractor
Extracts and reviews a SINGLE legal document against a defined set of review columns/fields, and returns a strict JSON object with one cell per column (value + verbatim source quote + location + confidence). Read-only. Spawned in parallel by the tabular-review skill (one extractor per file). Use whenever you need to…
token-engineer
Token-2022 extensions specialist for advanced token mechanics, token economics design, launch strategies, and liquidity management on Solana. Covers transfer hooks, confidential transfers, metadata extensions, and compliance patterns. Use when: Creating tokens with Token-2022 extensions, designing token economics…
DearLeader
Use when: making architecture decisions, defining C++ porting strategy, reviewing API design, resolving scope and priority questions, evaluating technical trade-offs, planning C#-to-C++ migration, reviewing code for architectural compliance.
FAI Azure Policy Expert
Azure Policy specialist — built-in/custom policy definitions, AI governance initiatives, compliance scanning, remediation tasks, and policy-as-code deployment patterns.