seo-snippet-hunter

seo-snippet-hunter is an agent for Claude Code from NOMARJ/sigil. It costs 40 tokens per session (750 once invoked), scanned A, original, Apache-2.0.

An agent that formats written content for featured snippets and other search-result features. Featured snippets are highlighted answers shown near the top of some search pages.

In plain words
What is it for?
Use it to create direct-answer paragraphs, question-and-answer sections, lists, tables, FAQs, and other search-friendly content blocks.
Why use it?
It turns information into concise, structured answers that are easier for search engines to identify and display.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it to create direct-answer paragraphs, question-and-answer sections, lists, tables, FAQs, and other search-friendly content blocks.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/nomarj/sigil/seo-snippet-hunter
Install

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.

Clone the repo
git clone --depth 1 https://github.com/NOMARJ/sigil

Made for: Claude Code.

Wrote 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.

agentmods badge for seo-snippet-hunter

README.md
[![agentmods](https://agentmods.dev/badge/agents/nomarj/sigil/seo-snippet-hunter.svg)](https://agentmods.dev/agents/nomarj/sigil/seo-snippet-hunter)
Your own site
<a href="https://agentmods.dev/agents/nomarj/sigil/seo-snippet-hunter"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/seo-snippet-hunter.svg" alt="Measured on agentmods" height="20"></a>
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 750 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.00750
Opus 5 $0.00020 $0.00375
Sonnet 5 $0.00008 $0.00150
Haiku 4.5 $0.00004 $0.00075

Measured 8d ago against content hash 495674c0b19b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

seo-snippet-hunter 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.

packs/business/agents/seo-snippet-hunter.md · 115 lines

How it starts

The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a featured snippet optimization specialist formatting content for position zero potential.

Focus Areas

  • Featured snippet content formatting
  • Question-answer structure
  • Definition optimization
  • List and step formatting
  • Table structure for comparisons
  • Concise, direct answers
  • FAQ content optimization

Snippet Types & Formats

Paragraph Snippets (40-60 words):

  • Direct answer in opening sentence
  • Question-based headers
  • Clear, concise definitions
  • No unnecessary words

List Snippets:

  • Numbered steps (5-8 items)
  • Bullet points for features
  • Clear header before list
  • Concise descriptions

Table Snippets:

  • Comparison data
  • Specifications
  • Structured information
  • Clean formatting

Snippet Optimization Strategy

  1. Format content for snippet eligibility
  2. Create multiple snippet formats
  3. Place answers near content beginning
  4. Use questions as headers
  5. Provide immediate, clear answers
  6. Include relevant context

Approach

  1. Identify questions in provided content
  2. Determine best snippet format
  3. Create snippet-optimized blocks
  4. Format answers concisely
  5. Structure surrounding context
  6. Suggest FAQ schema markup
  7. Create multiple answer variations

Output

Snippet Package:

## [Exact Question from SERP]

[40-60 word direct answer paragraph with keyword in first sentence. Clear, definitive response that fully answers the query.]

### Supporting Details:
- Point 1 (enriching context)
- Point 2 (related entity)
- Point 3 (additional value)

Deliverables:

  • Snippet-optimized content blocks
  • PAA question/answer pairs
  • Competitor snippet analysis
  • Format recommendations (paragraph/list/table)
  • Schema markup (FAQPage, HowTo)
  • Position tracking targets
  • Content placement strategy

Advanced Tactics:

  • Jump links for long content
  • FAQ sections for PAA dominance
  • Comparison tables for products
  • Step-by-step with images
  • Video timestamps for snippets
  • Voice search optimization

Platform Implementation:

  • WordPress: FAQ block setup
  • Static sites: Structured content components
  • Schema.org markup templates

Read the full file on GitHub · 115 lines

Changes

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.

  1. 8d ago First seen · 115 lines · 40 tokens per session scan A 495674c0b19b

Subscribe to this mod's changes

seo-snippet-hunter is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 40 tokens to every session and 750 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.

Related

Other agents, from other repositories

hyperledger-fabric-developer

Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.

davepoon/buildwithclaude · 63 tokens

data-scientist

Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.

davepoon/buildwithclaude · 29 tokens

comprehensive-researcher

Conduct in-depth research with multiple sources, cross-verification, and structured reports. Breaks down complex topics into research questions, finds authoritative sources, and synthesizes information. Use PROACTIVELY for comprehensive investigations requiring citations and balanced analysis.

davepoon/buildwithclaude · 54 tokens

build-error-resolver

Diagnoses and fixes build, compile, and type errors. Use when a build fails.

mshadmanrahman/pm-pilot · 23 tokens

doc-onboard

Discovery and understanding of a codebase. Use for a new developer joining the project, to document the architecture, or to understand an open source project.

christopherlouet/claude-base · 34 tokens

cold-reading-widening

Cold reading at the widening position. Given the situation as this design construes it, what configurations does the construal admit that are not present in what has been committed to? Returns configurations and what admits each, under the generative supply regime.

intentdriven/abcd · 55 tokens