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 marketingskills/seo --skill exceed-quality-thresholdgit clone --depth 1 https://github.com/marketingskills/seoWrote 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/marketingskills/seo/exceed-quality-threshold)<a href="https://agentmods.dev/skills/marketingskills/seo/exceed-quality-threshold"><img src="https://agentmods.dev/badge/skills/marketingskills/seo/exceed-quality-threshold/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/marketingskills/seo/exceed-quality-threshold"><img src="https://agentmods.dev/badge/skills/marketingskills/seo/exceed-quality-threshold.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.00115 | $0.02393 |
| Opus 5 | $0.00057 | $0.01196 |
| Sonnet 5 | $0.00023 | $0.00479 |
| Haiku 4.5 | $0.00012 | $0.00239 |
Grade A, and why
exceed-quality-threshold 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.
How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exceed Quality Threshold
Purpose
Determine what a page must do to become eligible and preferable for a connected query network. Compare like with like, identify the demonstrated lower and upper boundaries, and require a material usefulness difference rather than superficial imitation.
Treat "quality threshold" as a comparative SEO model, not a disclosed Google score or ranking factor. Separate observations from hypotheses and recommendations. Read references/evidence-and-guardrails.md before making claims about Google, Koray's framework, or prescriptive tactics.
Required inputs
Collect or infer:
- Primary query or topic
- Target page, draft, brief, or proposed resource
- Publishing site and intended source type
- Target market, language, device, and current date
- Intended audience and conversion/task goal
- Any first-party evidence, expertise, data, or tools available
Ask only for a missing input that would materially change the cohort or verdict. If no page exists, evaluate the proposed format and produce a build specification. If the site is unavailable, continue with a provisional page-level assessment and label source-level findings unknown.
Evidence rules
- Use live web search whenever available. SERPs, freshness, page contents, and reputations change.
- Record query, market, language, device when known, and date. Do not imply a neutral or universal SERP.
- Prefer direct inspection of ranking pages over snippets. Snippets cannot establish completeness, evidence, or page experience.
- Cite the pages used for decisive observations. Distinguish observed facts, reasonable inference, and unknowns.
- Never invent rankings, page contents, traffic, links, authority, authorship, methodology, or first-party evidence.
- If live search or page access is unavailable, use user-supplied exports or URLs and label the result
provisional; do not claim to have measured the current threshold. - Do not equate length, heading count, entity count, schema, images, or n-gram overlap with quality. Count an element only when it helps satisfy the task or establishes evidence.
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.
- 10d ago First seen · 239 lines · 115 tokens per session scan A b2facee8f878
exceed-quality-threshold is a skill published in the GitHub repository marketingskills/seo (3 stars, last pushed 1mo ago), licensed MIT. It adds 115 tokens to every session and 2,393 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-31.
Other skills, from other repositories
os-check-work
ALWAYS invoke this skill when the user asks about work done outside this session - "check work", "check the others", "check other sessions" - or to accept one: "the session is done, check it", "can we merge it" - in any language. You are the receiving party: treat the report as a claim, verify each part against…
os-done-or-not
ALWAYS invoke this skill when work wraps up or the user asks how it went - "done or not", "are we done", "what happened", "report" - in any language, and when a Stop hook asks for a session report. Produces a ten-line plain- language report: a lead, a checkmark table, and a verdict - fully done, anything needed from…
os-step-by-step
ALWAYS invoke this skill when you need the user to act - run a command, paste a secret, click, approve - and whenever they ask how to do something or say they do not know what to do: "step by step", "walk me through it", "what do I do", "what should I do", "I don't understand what to do", "explain what I need to do"…
os-what-could-go-wrong
ALWAYS invoke this skill before anything hard to undo gets agreed to - a contract, a purchase, a migration, a launch, a price change, a reorganisation - and whenever the user asks "what could go wrong", "what are we missing", "poke holes in this", or for a premortem or a red team, in any language. Assumes the decision…
os-ask-simple
ALWAYS invoke this skill before asking the user any technical question or offering options, and whenever they ask to be asked in plain words - "ask simple", "ask me simply", "ask me in plain words" - or ask if something is worth doing or if something simpler would do, in any language. Rewrites the question in plain…
os-whats-next
ALWAYS invoke this skill when the user asks what to do next, what is left, or what is blocked - "what's next", "what now", "what should we work on", "anything I can do" - in any language. This skill picks the next piece of work; when the user asks HOW to do a thing or says they do not understand what to do, that is…