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 cwinvestments/memstack --skill meta-tag-optimizergit clone --depth 1 https://github.com/cwinvestments/memstackWrote 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/cwinvestments/memstack/meta-tag-optimizer)<a href="https://agentmods.dev/skills/cwinvestments/memstack/meta-tag-optimizer"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/meta-tag-optimizer.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.00067 | $0.02903 |
| Opus 5 | $0.00034 | $0.01452 |
| Sonnet 5 | $0.00013 | $0.00581 |
| Haiku 4.5 | $0.00007 | $0.00290 |
Grade A, and why
memstack-seo-meta-tag-optimizer 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 3d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🏷️ Meta Tag Optimizer: Scanning and optimizing page meta tags...
Scans all pages for existing meta tags, identifies issues, and generates optimized replacements: titles, descriptions, Open Graph, canonical URLs, and robots directives.
Activation
When this skill activates, output:
🏷️ Meta Tag Optimizer, Scanning pages for meta tag issues...
Then execute the protocol below.
| Context | Status |
|---|---|
| User says "optimize meta tags" or "fix meta tags" | ACTIVE |
| User says "title tags" or "meta description" or "og tags" | ACTIVE |
| Improving SEO for specific pages | ACTIVE |
| Running a full site audit (broader scope) | DORMANT: use site-audit |
| Adding structured data / JSON-LD | DORMANT: use schema-markup |
Anti-patterns
| Trap | Reality Check |
|---|---|
| "Same meta description on every page" | Duplicate descriptions get ignored by Google. Each page needs unique, relevant meta. |
| "Title = just the page name" | "About" tells Google nothing. "About [Company] - [Key Differentiator]" ranks. |
| "OG tags are optional" | Without og:image, your shared links look broken on social. No image = no clicks. |
| "Canonical URLs don't matter" | Duplicate content splits ranking signals. Canonical tags consolidate authority to one URL. |
| "Longer titles rank better" | Google truncates after ~60 chars. Truncated titles look unprofessional and lose clicks. |
Protocol
Step 1: Scan All Pages
Identify every page and its current meta tags:
# Find all page/route files
find app/ pages/ src/ -name "*.tsx" -o -name "*.jsx" -o -name "*.html" 2>/dev/null | grep -v node_modules | grep -v "_\|layout\|loading\|error\|not-found"
# Next.js metadata exports
grep -rn "export const metadata\|export function generateMetadata" --include="*.tsx" --include="*.ts" . | grep -v node_modules
# Check for global/shared metadata
cat app/layout.tsx 2>/dev/null | head -30
Build the page inventory:
| Page | Route | Has Title | Has Description | Has OG | Has Canonical |
|---|---|---|---|---|---|
| Homepage | / |
? | ? | ? | ? |
| About | /about |
? | ? | ? | ? |
| Pricing | /pricing |
? | ? | ? | ? |
| Blog index | /blog |
? | ? | ? | ? |
| Blog post | /blog/[slug] |
? | ? | ? | ? |
| ... | ... | ... | ... | ... | ... |
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.
- 3d ago Changed 7d04b269f350
- 3d ago First seen · 285 lines · 67 tokens per session scan A 24e7ae2b97f0
memstack-seo-meta-tag-optimizer is a skill published in the GitHub repository cwinvestments/memstack (419 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 2,903 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-09-03.
Other skills, from other repositories
atomic-writing
One voice for every file the repo ships: README, docs/guides/, docs/reference/, docs/spec/, docs/design/, docs/research/, docs/wiki/, CLAUDE.md, and the prompt artifacts under commands/, agents/, skills/, rules/, and output-styles/. Clear, direct, technical, and visual wherever the content has a shape. No marketing…
atomic-documentation
Diff-driven documentation surface classifier. Given a diff (staged, branch, or range), reads the project's indexed ## Documentation surfaces table from CLAUDE instructions, matches the diff against it, and emits a structured list of proposed edits. Two modes: maintenance (commit flow — stale/incomplete only, never…
atomic-visual-options
Planning-phase visual comparison aid. Renders 2-4 side-by-side variants per decision dimension as a single throwaway, self-contained HTML file and captures the user's pick as typed terminal codes (e.g. "A2 B3"). Auto-fires on phrases like "show me a few options", "mock up some variants", "let me see this side by…
atomic-git-discipline
Compressed commit message and PR body generator. Cuts noise from both while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious; PR bodies state only what the diff can't show, 120 words max. Use when user says "write a commit", "commit message", "generate…
atomic-debug
Hypothesis-driven debugging skill. Use when a bug, test failure, crash, or unexpected behavior is reported. Auto-trigger on error pastes or "broken/doesn't work/failing" language. Explicit invocation: /atomic-debug. Output: symptom statement → hypothesis table → cheapest test first → root cause. No symptom-patching.…
atomic-wiki
Conversational wiki and capture-bucket routing. Fires when the user wants a place, space, or folder for notes, research, tickets, raw dumps, or knowledge capture — checks the block in /.claude/CLAUDE.md; if the cwd is under a registered realm, creates the folder as a bucket via atomic wiki bucket add rather than a…