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/bestdeejay-design/agent-skillsWrote 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/commands/bestdeejay-design/agent-skills/seo-structure)<a href="https://agentmods.dev/commands/bestdeejay-design/agent-skills/seo-structure"><img src="https://agentmods.dev/badge/commands/bestdeejay-design/agent-skills/seo-structure.svg" alt="Measured on agentmods" 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.00050 | $0.00594 |
| Opus 5 | $0.00025 | $0.00297 |
| Sonnet 5 | $0.00010 | $0.00119 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
seo-structure 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 8d 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.
What it actually says
You are a specialist in website architecture and structural SEO. Analyze the project structure to identify internal linking issues, URL, hierarchy and page authority distribution.
1. Site mapping
First identify all pages of the project:
- In Next.js/Nuxt projects:
pages/orapp/folder - In Astro projects:
src/pages/folder - In Hugo/Jekyll projects:
content/folder - Static HTML: all
.htmlfiles - Check the
sitemap.xmlif present
Create a map of all site URLs.
2. Architecture analysis
URL hierarchy
- Do URLs reflect the content hierarchy? (
/blog/categoria/articulo) - Are there URLs more than 3 levels deep? (crawl issue)
- Are URLs descriptive and keyword-rich?
- Are there parameters in URLs that should be clean paths?
Click depth
- How many clicks does a user (or crawler) need to reach each page from the home?
- Pages more than 3 clicks deep = problem
- Orphan pages = no internal links pointing to them
Internal Linking
- Do the main pages have enough internal links pointing to them?
- Are there broken internal links?
- Does the anchor text of internal links contain descriptive keywords?
- Is there an HTML sitemap page for users?
Authority distribution (internal PageRank)
- Does the home page link to the most important pages?
- Do important pages link to each other?
- Are there pages that receive a lot of traffic but few internal links?
3. Output report
## SEO Architecture Report — [project]
**Date:** [date]
**Total pages:** X
### Detected site map
/ (home) ├── /page-1 │ ├── /page-1/sub-1 │ └── /page-1/sub-2 ├── /page-2 └── ...
### 🔴 Critical structure issues
- [specific issue with files and paths]
### 🟡 Improvement opportunities
- [opportunity with suggested implementation]
### Suggested Internal Links
| Source page | Target page | Suggested anchor text |
|--------------|---------------|---------------------|
| [url] | [url] | [text] |
### Detected orphan pages
- [list of pages without internal links]
### Recommended architecture plan
[Description of the ideal structure for the site]
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.
- 8d ago First seen · 85 lines · 50 tokens per session scan A 1cc9d576bea2
seo-structure is a command published in the GitHub repository bestdeejay-design/agent-skills (5 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 594 once invoked, about $0.0003 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 commands, from other repositories
statusbar
Show current status-bar config and list available styles + themes.
accessibility-setup
Configura las preferencias de accesibilidad de Savia para adaptarse a tus necesidades.
accessibility-mode
Toggle rápido de accesibilidad — activa, desactiva o muestra el estado.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
terse
Switch reply compression level — /terse [lite|full|ultra|off]. Complements RTK (input savings) with output-side savings.
rewind-summary
Capture a carry-forward summary of work done since a checkpoint so it survives a native rewind/Restore. Run before rewinding.