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 divyamrastogi/cws-featured-badge-skill --skill cws-featured-badgegit clone --depth 1 https://github.com/divyamrastogi/cws-featured-badge-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/skills/divyamrastogi/cws-featured-badge-skill/cws-featured-badge)<a href="https://agentmods.dev/skills/divyamrastogi/cws-featured-badge-skill/cws-featured-badge"><img src="https://agentmods.dev/badge/skills/divyamrastogi/cws-featured-badge-skill/cws-featured-badge/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/divyamrastogi/cws-featured-badge-skill/cws-featured-badge"><img src="https://agentmods.dev/badge/skills/divyamrastogi/cws-featured-badge-skill/cws-featured-badge.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.00111 | $0.01146 |
| Opus 5 | $0.00056 | $0.00573 |
| Sonnet 5 | $0.00022 | $0.00229 |
| Haiku 4.5 | $0.00011 | $0.00115 |
Grade A, and why
cws-featured-badge 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 12d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chrome Web Store Featured Badge Audit
Audit a Chrome extension codebase + store listing against Google's published criteria for the Featured badge (manually reviewed by the CWS team) and the Established Publisher badge (granted on publisher standing), then produce a report with a prioritized fix plan.
Two facts shape every audit:
- Badges cannot be bought or expedited. The only lever is genuinely meeting the criteria. Never suggest gaming tactics (incentivized reviews, keyword stuffing); these violate program policies and disqualify the extension.
- Featured is a human review. The reviewer checks best-practice adherence, UX quality, modern platform APIs, privacy respect, and listing quality. The audit must therefore judge quality, not just tick boxes — "has screenshots" passes a checklist; "screenshots are clear, uncluttered, and show real functionality" passes a review.
Workflow
1. Gather evidence
Collect before judging. From the codebase (ask the user for the repo path if not obvious):
manifest.json— manifest version, permissions, host permissions, name, description, icons- Privacy policy file/URL and what data the code actually collects (search for network calls, analytics, storage of user data)
- Onboarding surfaces: first-install pages, popup, options page
- Test setup (E2E tests count toward the "tested across environments" practice)
- bfcache hazards:
unloadhandlers, WebSocket/WebRTC in content scripts - Store assets: icon sizes, screenshots, promo tile (440×280), marquee (1400×560), listing copy if checked into the repo
From the user (these live in the CWS dashboard and usually aren't in the repo): publisher verification status, account standing, current listing text/category, rating and review count, whether core features need login/payment. If the extension is published, fetch its public listing page to assess copy, screenshots, rating, and category directly. Don't guess at dashboard-only facts — mark them "needs manual check" instead.
What ships with it
2 files 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.
- 12d ago First seen · 111 lines · 111 tokens per session scan A 93fa8ef97763
cws-featured-badge is a skill published in the GitHub repository divyamrastogi/cws-featured-badge-skill (13 stars, last pushed 2mo ago), licensed MIT. It adds 111 tokens to every session and 1,146 once invoked, about $0.0006 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-30.
Other skills, from other repositories
chief-revenue-officer
Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not…
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…
seo-strategy
Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…
financial-statement-analysis
Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
youtube-producer
Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a…