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 SunrisesIllNeverSee/agent-universe --skill testing-seogit clone --depth 1 https://github.com/SunrisesIllNeverSee/agent-universeWrote 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/sunrisesillneversee/agent-universe/testing-seo)<a href="https://agentmods.dev/skills/sunrisesillneversee/agent-universe/testing-seo"><img src="https://agentmods.dev/badge/skills/sunrisesillneversee/agent-universe/testing-seo/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/sunrisesillneversee/agent-universe/testing-seo"><img src="https://agentmods.dev/badge/skills/sunrisesillneversee/agent-universe/testing-seo.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.00039 | $0.00587 |
| Opus 5 | $0.00019 | $0.00293 |
| Sonnet 5 | $0.00008 | $0.00117 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
testing-seo scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- After merge, spot-check production via `curl -s https://signomy.xyz/<page> | grep 'name="description"'` How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing SEO Changes — signomy.xyz
Architecture
- Frontend: Vercel (
signomy.xyzDNS) — serves static HTML fromfrontend/withcleanUrls: true - Backend: Railway — only handles
/api/*,/mcp,/health,/ws/*,/docs/*via Vercel rewrites - Velvet Rope middleware runs on Railway only — does NOT affect Googlebot crawling pages on Vercel
Vercel Preview Limitation
Vercel preview deployments may have deployment protection (SSO) enabled, returning 401. If this happens:
- Test source files directly via grep/inspection
- Curl production to establish a baseline (confirm the problem exists today)
- After merge, spot-check production via
curl -s https://signomy.xyz/<page> | grep 'name="description"'
Key Test Commands
Check meta descriptions exist
for f in frontend/*.html; do
name=$(basename "$f" .html)
desc=$(grep -oP 'name="description" content="\K[^"]+' "$f" | head -1)
echo "$name: ${desc:-MISSING}"
done
Check canonicals
for f in frontend/*.html; do
name=$(basename "$f" .html)
canonical=$(grep -oP 'rel="canonical" href="\K[^"]+' "$f" | head -1)
echo "$name: ${canonical:-NO CANONICAL}"
done
Verify redirects on production
curl -sI -o /dev/null -w "%{http_code} %{redirect_url}" "https://signomy.xyz/<path>"
Check robots.txt
curl -s https://signomy.xyz/robots.txt | grep -i sitemap
Common Issues
sitemap.htmlcanonical was broken (pointed to/mapsitewhich 404'd on Vercel). The canonical should match the actual serving URL.sitemap.xmlandsitemap-v2.xmlwere identical duplicates. Keep only one inrobots.txt.- Pages with
og:descriptionbut no<meta name="description">— Google uses the standard meta tag, not OG. www.signomy.xyzredirects with 307 (temporary) instead of 301. This is a Vercel dashboard setting, not configurable invercel.json.
Devin Secrets Needed
None — SEO testing uses only public curl requests and source file inspection.
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.
- 9d ago First seen · 57 lines · 39 tokens per session scan A c459e9587aae
testing-seo is a skill published in the GitHub repository SunrisesIllNeverSee/agent-universe (1 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 587 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
frontend-feature
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.
pytest-suite
Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.
react-web
React web development with hooks, React Query, Zustand.
storybook-stories
Write Storybook stories for PostHog UI components. Covers the provider stack stories run inside, the key gotcha that tRPC/useHostTRPC queries never resolve in Storybook (so data-fetching components render empty), and the pure-presentational split that makes a component storyable. Use when adding or fixing a…
organizing-conversations-code
File layout for the conversations product. Use when adding, moving, renaming, or reviewing files under products/conversations/ — especially frontend components, scenes, helpers, and tests. Conversations React components live in their own folder under products/conversations/frontend/components/, never as loose files in…
visual-verify-ui
Wraps the browser tool into a dedicated visual QA testing skill for frontend work.