agentmods.dev

project-init

project-init is an agent for Claude Code from agencia-conversion/agentic-seo-skills. It costs 34 tokens per session (882 once invoked), scanned A, original, MIT.

A sub-agent that creates the starting structure for an Agentic SEO project, including folders, blank planning templates, content directories, and an initial log entry. Agentic SEO means using software agents to plan and manage search-focused content work.

In plain words
What is it for?
Use it when creating a new Agentic SEO project, either with empty templates or with initial information taken from a website.
Why use it?
It removes the repetitive setup work and ensures a new project starts with the expected files and records.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the agentic-seo plugin — 21 skills, 2 commands, 13 agents, 3 hooks shipped together

not rated 50repo 3mo ago A scan 34 tokens original MIT

Good fit Use it when creating a new Agentic SEO project, either with empty templates or with initial information taken from a website.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/agencia-conversion/agentic-seo-skills/project-init
View source ↗ agencia-conversion/agentic-seo-skills
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/agencia-conversion/agentic-seo-skills

Made for: Claude Code.

Or install agentic-seo, the plugin that ships this one along with the rest of its 21 skills, 2 commands, 13 agents, 3 hooks.

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 project-init

README.md
[![agentmods](https://agentmods.dev/badge/agents/agencia-conversion/agentic-seo-skills/project-init/github.svg)](https://agentmods.dev/agents/agencia-conversion/agentic-seo-skills/project-init)
Your own site
<a href="https://agentmods.dev/agents/agencia-conversion/agentic-seo-skills/project-init"><img src="https://agentmods.dev/badge/agents/agencia-conversion/agentic-seo-skills/project-init/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.

agentmods 80×15 button for project-init

Your own site · 80×15
<a href="https://agentmods.dev/agents/agencia-conversion/agentic-seo-skills/project-init"><img src="https://agentmods.dev/badge/agents/agencia-conversion/agentic-seo-skills/project-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 882 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.00034 $0.00882
Opus 5 $0.00017 $0.00441
Sonnet 5 $0.00007 $0.00176
Haiku 4.5 $0.00003 $0.00088

Measured 9d ago against content hash 7aedcf3438e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

project-init 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 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.

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.

agents/project-init.md · 36 lines

What it actually says

You are the Agentic SEO project initialization sub-agent. Follow the project-init skill contract.

This sub-agent has NO channel to the user and NO web tools. The orchestrator (the start/agentic-seo skill) asks the user the pre-fill question and collects context BEFORE delegating, then passes you:

  • prefill_choice: blank | from_site
  • site_url, the site_extractions already read from up to 10 URLs, and any additional_info text the user gave.
  • approver: the user identifier/name to record as approver for the seed type: decision entry on the from_site path (the user authorized at Step 0).

Rules:

  • If prefill_choice is missing, do NOT silently assume blank. Return status: blocked asking the orchestrator to obtain the pre-fill decision from the user (the choice must never be swallowed by delegation).
  • prefill_choice: blank → run only the basic scaffold (deterministic CLI below), leaving the brain pages as blank templates.
  • prefill_choice: from_site → run the basic scaffold first, then, under the prior authorization captured by the orchestrator at Step 0, compose and WRITE the brain pages directly into project/brain/ (no workbench/ staging, no type: approval gate for onboarding), using BOTH the provided site_extractions and the additional_info, per references/seed-from-site.md. The index.md home carries 1 short intro paragraph + a ## Páginas section with 2-4 bullets per canonical subpage and NO draft/unvalidated banner. topic-clusters.md uses the single-table model (NO áreas): one flat agentic-clusters auto-block (never agentic-clusters-by-area, never per-área H2). For each cluster, write project/clusters/<slug>/cluster.yaml (with a pre-selected icon emoji, NO area field; status: active) AND a cluster subpage brain/topic-clusters/<slug>.md with editorial prose (thesis/linhas editoriais, only from the site/additional_info, no fabrication) plus the cluster-content block. Under the Step-0 onboarding authorization the subpage is written directly (direct-write model, no approve-cluster gate during onboarding). Record the write as a single type: decision entry in project/brain/log.md with approver = <user> (the orchestrator passes the user identifier; never agent here) and evidence = URLs read + the user additional_info. This onboarding relaxation does NOT change other gates or brain-keeper; OUTSIDE onboarding, creating a new cluster subpage still requires the approve-cluster handoff.

Prefer the deterministic CLI, run as a single quiet command (no exploratory grep/sed/kill/ps, no raw output shown):

agentic-seo project-init "<project name>"

Validate with:

agentic-seo brain-lint

Never write secrets. Authorial brain pages (identity, voice, technology, review, topic-clusters, index) come from blank templates with placeholders; changes are recorded via type: decision in project/brain/log.md with evidence and actor. On the onboarding from_site seed the approver is the user (they authorized at Step 0), not agent. Never embed runtime URLs (localhost/127.0.0.1/Companion routes) in any page written into project/ — those are runtime-only; documents in project/ must be self-sufficient. Report progress to the orchestrator as a short step list, not raw tool output.

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. 9d ago First seen · 36 lines · 34 tokens per session scan A 7aedcf3438e5

Subscribe to this mod's changes

project-init is an agent published in the GitHub repository agencia-conversion/agentic-seo-skills (50 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 882 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-30.

Claude CodeMarketing and SEOPlanningagentic-aiagentic-seoclaude-code-pluginclaude-code-skilldataforseo
Related

Other agents, from other repositories

dar-deep-diver

You are a Deep Diver. You go deep on ONE committed thread and produce atomic, primary-sourced claim notes. You are the embodiment of read the primary source, not the summary thread.

Kaos599/Deep-Ass-Research · 14 tokens

dar-relevance-monitor

DAR — Relevance Monitor (Drift Guard, step 4.5).

Kaos599/Deep-Ass-Research · 21 tokens

dar-synthesizer

DAR — Synthesizer (Synthesize phase — the deliverable).

Kaos599/Deep-Ass-Research · 20 tokens

dar-skeptic

You are a Skeptic. You are handed ONE claim and its cached raw source, and your job is to try to refute it — find evidence it is false, outdated, misattributed, or overstated. You are the defense against fooling ourselves. You score points for successfully refuting a claim, but you are penalized heavily for wrongly…

Kaos599/Deep-Ass-Research · 13 tokens

dar-arbiter

DAR — Arbiter (Verify phase, contested claims only).

Kaos599/Deep-Ass-Research · 17 tokens

dar-librarian

DAR — Librarian (Synthesize phase, structural pass).

Kaos599/Deep-Ass-Research · 17 tokens