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 AntonioBlago/peec-ai-skills --skill peec-reportgit clone --depth 1 https://github.com/AntonioBlago/peec-ai-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/skills/antonioblago/peec-ai-skills/peec-report)<a href="https://agentmods.dev/skills/antonioblago/peec-ai-skills/peec-report"><img src="https://agentmods.dev/badge/skills/antonioblago/peec-ai-skills/peec-report/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/skills/antonioblago/peec-ai-skills/peec-report"><img src="https://agentmods.dev/badge/skills/antonioblago/peec-ai-skills/peec-report.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.00080 | $0.02186 |
| Opus 5.5 | $0.00032 | $0.00874 |
| Sonnet 5.5 | $0.00016 | $0.00437 |
| Haiku 4.5 | $0.00008 | $0.00219 |
Grade A, and why
peec-report 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 2mo 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Growth Loop Reporter
Role
Close the loop. Three questions per cycle, answered in ≤400 words:
- What moved? — visibility trend per prompt, cluster, zone
- Why? — which specific investment caused which lift
- What next? — 3 prioritized actions, at least 1 stop-doing
Output is a short narrative + actions, not a dashboard. Fifteen charts don't get read. 400 words do.
Input
project_id— Peec projectreporting_window—weekly|monthly|quarterly- optional
baseline_date— default 28 / 90 / 180 days back - optional
include_clusters— auto-detected viazone:*tags ifpeec-clusterhas run
Output
- One narrative at
<project>/growth_loop/YYYY-MM-DD_report.md(schema below) - One
learnings.jsonwith winners / losers / surprises / next_actions / stop_doing — consumed by the nextpeec-clusterandpeec-outreachruns as priors
When to use
- Weekly for active projects with running content + outreach
- Monthly for retainer projects in maintenance
- Quarterly as strategy review — feeds the next
peec-clusterrun - After a launch, publication, or new zone going live
Do not use when:
- Project has <4 weeks of history (too little signal)
- No content or outreach actions in the window (nothing to learn)
Pipeline
0. Pre-flight — setup state required
Per _shared/SETUP_STATE.md, this skill refuses to run without a completed setup:
Read <project>/growth_loop/setup_state.json
If missing OR completed_at missing OR phases_completed lacks
{competitors, prompts, topics, tags}:
STOP. Output:
"No Peec setup state found at <project>/growth_loop/setup_state.json.
Run /peec-setup first."
If completed_at older than 90 days: WARN once, continue.
Use peec_project_id from state — don't re-resolve via list_projects.
1. Pull time-series of core metrics
# Overall brand visibility trend
mcp__peec-ai__get_brand_report(
project_id, start_date=baseline, end_date=now,
dimensions=["date"],
filters=[{field: "brand_id", operator: "in", values: [own_brand_id]}]
)
# Per prompt (top-N by weight)
mcp__peec-ai__get_brand_report(
project_id, start_date=baseline, end_date=now,
dimensions=["prompt_id", "date"],
filters=[{field: "brand_id", operator: "in", values: [own_brand_id]}]
)
# Per zone (if zone:* tags exist)
for each zone_tag:
mcp__peec-ai__get_brand_report(
project_id, start_date=baseline, end_date=now,
dimensions=["tag_id", "date"],
filters=[{field: "tag_id", values: [zone_tag_id]}]
)
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.
- 2mo ago First seen · 240 lines · 80 tokens per session scan A 713ef6ff55f6
peec-report is a skill published in the GitHub repository AntonioBlago/peec-ai-skills (10 stars, last pushed 6mo ago), licensed MIT. It adds 80 tokens to every session and 2,186 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
seo-content-blog
Spec, audit, competitor benchmark and build for blog articles and the blog template, so a post ranks on Google and gets cited by AI engines (ChatGPT, Perplexity, AI Overviews). Input: a keyword, topic, draft or post URL. Phase 1 spec: BLOG rows on top of the common page spec, covering the 12-element answer-first…
seo-content-collection-page
Spec, audit, competitor benchmark and build for e-commerce collection, category and product listing pages (PLPs) on Shopify, WooCommerce, Magento, BigCommerce, PrestaShop or a custom store. Runs four phases: the collection spec (COL-01 to COL-24 plus the common rows), an audit of the live page with the bundled…
seo-content-comparison-page
Spec, audit, competitor benchmark and build for the bottom-funnel pages that capture buyers at the decision moment: 'X vs Y', 'alternatives to X', 'best X for Y', the comparison hub, and audience or segment pages ('for agencies', 'for freelancers'). Runs four phases: the CMP spec with stable IDs on top of the common…
seo-content-product-page
Spec, audit, competitor benchmark and build for e-commerce product pages (PDPs), so they rank in Google and get recommended by the AI assistants that now link products directly. Input: a product page URL or a product brief (Shopify, WooCommerce, Magento, BigCommerce, PrestaShop, Wix, Webflow or custom). Runs four…
seo-content-service-page
Spec, audit, competitor benchmark and build for service pages and service landing pages (agencies, consultants, coaches, trades, clinics, law firms, SaaS), plus region and city pages. Input: a service, the business, a target area, the page URL if any. Runs four phases: the spec (SVC-01 to SVC-24 on top of the common C…
seo-local
Run spec, audit, competitor benchmark and build for local visibility, on the two assets a local business owns: the location page and the Google Business Profile, plus reviews and NAP citations. Spec: LOC, GBP, REV and CIT requirements with IDs. Audit: seoaudit.py and sectionaudit.py --type location on the page, a…