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 T4wroot/agentic-seo --skill disclosuregit clone --depth 1 https://github.com/T4wroot/agentic-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/t4wroot/agentic-seo/disclosure)<a href="https://agentmods.dev/skills/t4wroot/agentic-seo/disclosure"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/disclosure/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/t4wroot/agentic-seo/disclosure"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/disclosure.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.00066 | $0.00606 |
| Opus 5.5 | $0.00026 | $0.00242 |
| Sonnet 5.5 | $0.00013 | $0.00121 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
disclosure-page-generator 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 1mo 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.
This is a copy
100% identical to disclosure-page-generator — 67 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pages: Disclosure
Guides disclosure pages for affiliate links, sponsored content, and paid partnerships. Required for FTC compliance (US) and similar regulations. Builds trust and reduces legal risk.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for affiliate/partnership model.
Identify:
- Type: Affiliate, sponsored, paid partnership, referral
- Scope: Site-wide, specific pages, or both
- Regions: US (FTC), EU, other
- Placement: Standalone page; link from footer, near affiliate content
Page Structure
| Section | Purpose |
|---|---|
| Headline | "Disclosure" or "Affiliate Disclosure" |
| Summary | We may earn from qualifying purchases; links may be affiliate |
| Details | How it works; what we recommend; no extra cost to you |
| Transparency | We only recommend products we believe in |
| Contact | Questions; link to contact |
Best Practices
FTC Compliance (US)
- Clear and conspicuous: Not buried; visible near affiliate content
- Before the click: Disclosure before user clicks affiliate link
- Plain language: "We may earn a commission" not legalese
Placement
- Footer link: "Disclosure" in every page footer
- Near content: Short disclosure above/below affiliate sections
- Standalone page: Full disclosure at /disclosure
Content
- Honest: Explain relationship; no misleading claims
- Concise: One page; avoid excessive length
- Update: When model changes
Output Format
- Headline and summary
- Full disclosure copy
- Placement guidance (footer, in-content)
- Legal note (consult lawyer for jurisdiction)
Related Skills
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.
- 1mo ago First seen · 67 lines · 66 tokens per session scan A 96e125ae07fa
disclosure-page-generator is a skill published in the GitHub repository T4wroot/agentic-seo (15 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 606 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to disclosure-page-generator, differing in 67 lines, and is treated as a copy.
Other skills, from other repositories
legal-page-generator
When the user wants to create, optimize, or structure legal pages (Privacy, Terms, etc.). Also use when the user mentions "privacy policy," "terms of service," "legal pages," "cookie policy," "terms and conditions," "legal footer," "legal section," "compliance pages," or "legal requirements." For Privacy Policy…
refund-page-generator
When the user wants to create or optimize a refund or return policy page. Also use when the user mentions "refund policy," "return policy," "money-back guarantee," "returns and refunds," "refund page," "return process," "refund terms," "satisfaction guarantee," "cancellation policy," or "withdrawal right." For legal…
privacy-page-generator
When the user wants to create, optimize, or structure Privacy Policy page. Also use when the user mentions "privacy policy," "privacy page," "data protection," "GDPR compliance," "privacy notice," "data privacy," "CCPA," "cookie policy," or "personal data." For legal overview page, use legal-page-generator.
terms-page-generator
When the user wants to create, optimize, or structure Terms of Service page. Also use when the user mentions "terms of service," "terms and conditions," "terms of use," "user agreement," "ToS," "legal terms," "service agreement," or "terms page." For legal overview page, use legal-page-generator.
cookie-policy-page-generator
When the user wants to create or optimize a cookie policy page. Also use when the user mentions "cookie policy," "cookies," "cookie consent," "GDPR cookies," "cookie banner," "cookie notice," "tracking cookies," or "cookie settings." For legal overview, use legal-page-generator.
brand-protection
When the user faces brand impersonation, fake websites, phishing sites, or trademark infringement. Also use when the user mentions "fake site," "impersonation," "phishing site," "trademark infringement," "domain squatting," or "brand abuse." For monitoring, use brand-monitoring.