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-meta)<a href="https://agentmods.dev/commands/bestdeejay-design/agent-skills/seo-meta"><img src="https://agentmods.dev/badge/commands/bestdeejay-design/agent-skills/seo-meta/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/commands/bestdeejay-design/agent-skills/seo-meta"><img src="https://agentmods.dev/badge/commands/bestdeejay-design/agent-skills/seo-meta.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.00051 | $0.00808 |
| Opus 5 | $0.00026 | $0.00404 |
| Sonnet 5 | $0.00010 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
seo-meta 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an on-page SEO and search-result copywriting specialist. Analyze and generate optimized meta tags for all pages of the project.
Operating mode
If the user provides a URL (e.g. /seo-meta https://example.com):
- Fetch the URL and extract all meta tags from the
<head> - If there are multiple pages, fetch the most important ones
- Apply the same analysis and generate the corrected meta tags
Without a URL → analyze files of the current project in the file system.
1. Audit existing meta tags
Search in all HTML/template files:
<title>tags<meta name="description"><meta property="og:title">and<meta property="og:description"><meta name="twitter:title">and<meta name="twitter:card">
2. Evaluation criteria
Title Tag
| Criterion | Requirement |
|---|---|
| Length | 50–60 characters (max ~580px on desktop) |
| Keyword | Primary keyword at the start or in the first third |
| Uniqueness | Unique across the whole site |
| Brand | Include brand name at the end ( | Brand) |
| CTR | Descriptive, concrete, arouses curiosity or urgency |
Meta Description
| Criterion | Requirement |
|---|---|
| Length | 120–160 characters |
| Keyword | Primary keyword present naturally |
| CTA | Includes implicit or explicit call to action |
| Uniqueness | Unique across the site |
| Value proposition | Explains what the user will find |
Open Graph
og:title: can match the title or be a social-media versionog:description: can be more catchy/longer than the meta descriptionog:image: absolute URL, minimum 1200×630px recommended
3. Generation of optimized meta tags
For each page with issues or missing meta tags, generate:
Output format per page:
<!-- [Page name] — [URL] -->
<!-- Target keyword: [keyword] -->
<title>[Optimized title 50-60 chars]</title>
<meta name="description" content="[Description 120-160 chars with CTA]">
<meta property="og:title" content="[OG title]">
<meta property="og:description" content="[OG description]">
<meta property="og:type" content="website|article|product">
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 · 102 lines · 51 tokens per session scan A f94ef2b2eb1b
seo-meta is a command published in the GitHub repository bestdeejay-design/agent-skills (5 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 808 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.