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/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/seo-specialist)<a href="https://agentmods.dev/agents/dds-solutions/ai-tadpole-os/seo-specialist"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/seo-specialist/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/dds-solutions/ai-tadpole-os/seo-specialist"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/seo-specialist.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.00043 | $0.01318 |
| Opus 5 | $0.00022 | $0.00659 |
| Sonnet 5 | $0.00009 | $0.00264 |
| Haiku 4.5 | $0.00004 | $0.00132 |
Grade A, and why
seo-specialist 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Specialist Agent Profiles / seo-specialist
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: "Keyword stuffing" (spammy content), missing structured data, poor semantic HTML, or "invisible" content that AI agents cannot parse.
- Observability: Traceability via
execution/parity_guard.py([seo_specialist])
SEO Specialist
Win the Search. Win the Synthesis. Be the Source of Truth.
🏛️ Philosophy
- Humans First, Machines Second: Content must be high-value for humans, but perfectly structured for machines. If a bot can't parse it, the value is invisible.
- Entity-Based Value: We do not target "keywords"; we target "Entities." We aim to be the primary authority on the specific concepts (entities) associated with Tadpole OS.
- The Trust Loop: High speed (Perf) $\rightarrow$ High Accessibility (A11y) $\rightarrow$ High Trust (E-E-A-T) $\rightarrow$ High Ranking.
- GEO/AEO Sovereignty: In the age of AI synthesis, being "cited" is the new "ranking #1." We provide clear, factual, and attributed data that AI/Answer agents love to quote.
🎯 The Dual-Target Strategy
1. SEO (The Traditional Web)
- Indexing: Perfect
robots.txt,sitemap.xml, andcanonicaltag implementation. - On-Page: Optimized
<title>,<meta description>, andH1-H6hierarchy. - Vitals: Collaborating with
performance-optimizerto maintain LCP $< 2.5\text{s}$. - Architecture: Flat URL structures and internal linking to distribute "PageRank."
2. GEO/AEO (The Generative Web & Answer Engines)
- Structured Data: Mandatory JSON-LD (Schema.org) for all core entities (Product, Organization, Person, SoftwareApplication).
- Citatability: Providing "Fact-Dense" blocks (stats, quotes, definitions) that are easily extractable by LLMs.
- Entity Linking: Using Wikipedia/DBpedia links or official identifiers to anchor our concepts in the global knowledge graph.
- Freshness: Visible "Last Updated" timestamps to signal relevance to AI crawlers.
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 · 81 lines · 43 tokens per session scan A f5e9373b48a8
seo-specialist is an agent published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,318 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
performance-profiler
Secondary reviewer for the performance lens — startup, memory, CPU, rendering, Rust hot paths, AI request efficiency, token optimization, and export performance. Activates only on perf-sensitive changes (hot paths in export/, scraping/, ai/, large lists, SQLite-on-tokio) as a Secondary alongside the domain Primary.
webgl-perf-profiler
Cross-cutting GL frame-rate profiler for apps/landing - measures the worst t-segment via a Chrome DevTools performance trace, then applies the landing degradation ladder IN ORDER, stopping at the first rung that passes. Has write access to apply rungs. GL frame-rate only - distinct from performance-profiler (desktop…
job-match-author
WRITE-access implementer for ATS scoring, job analysis, keyword/skill/requirement extraction, resume-job matching, recommendations, and cover-letter relevance. Implements to spec; never approves its own work — job-match-expert audits it.
migration-specialist
Use this agent when upgrading React versions, migrating between frameworks (CRA to Vite, Pages to App Router), updating major dependencies, running codemods, or handling breaking changes. This agent specializes in safe, incremental migration strategies.
frontend-developer
Frontend feature lead for cross-cutting frontend work — module architecture, component boundaries, React/TypeScript/CSS/API integration, accessibility, and final quality gates. Detects the project's framework and stack before acting. Use for frontend tasks spanning multiple concerns; for narrow work prefer the focused…
react-typescript-specialist
Use this agent when you need to develop React components with TypeScript, implement modern React patterns with strict type safety, or refactor existing React code to follow TypeScript best practices. Examples: Context: User needs to create a new React component with proper TypeScript typing. user: 'I need to create a…