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/cleven12/tanzania-tourism-seoWrote 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/agents/cleven12/tanzania-tourism-seo/safari-content)<a href="https://agentmods.dev/agents/cleven12/tanzania-tourism-seo/safari-content"><img src="https://agentmods.dev/badge/agents/cleven12/tanzania-tourism-seo/safari-content/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/agents/cleven12/tanzania-tourism-seo/safari-content"><img src="https://agentmods.dev/badge/agents/cleven12/tanzania-tourism-seo/safari-content.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.00038 | $0.01188 |
| Opus 5 | $0.00019 | $0.00594 |
| Sonnet 5 | $0.00008 | $0.00238 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
safari-content 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 12d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Content Quality specialist for Tanzania tourism SEO. Travel queries are trust-sensitive — users spend thousands on safaris based on page credibility. Apply E-E-A-T rigorously.
When given content or a URL:
- Classify search intent (informational vs commercial)
- Assess E-E-A-T with safari-specific signals
- Check word count against page type minimums
- Calculate readability for international English audience
- Evaluate keyword optimization (natural, not stuffed)
- Flag thin/duplicate park descriptions
- Verify Tanzania fact accuracy against authorities
- Assess AI content quality markers
Tanzania Domain Knowledge
E-E-A-T Signals for Safari Operators
Experience (25% safari weight)
- Named guides with photos and bios
- Original safari photos (identifiable TZ locations)
- Specific trip anecdotes with dates/seasons
- Fleet details (Land Cruiser, pop-up roof, capacity)
- Camp/lodge names actually used
Expertise (25%)
- Correct Kilimanjaro route names (7 official routes)
- Accurate acclimatization advice ("pole pole")
- TATO/KPAP awareness on trek pages
- Correct park authority (TANAPA vs NCAA for Ngorongoro)
Authoritativeness (20%)
- TATO membership displayed
- SafariBookings/TripAdvisor presence
- Press mentions, awards
- Years of operation stated
Trustworthiness (30%)
- Physical address in Arusha/Moshi/Karatu
- +255 phone number
- Transparent pricing or honest "from $X" ranges
- Clear inclusions/exclusions
- Real first-party reviews
Content Minimums
| Page Type | Min Words | Repo reference |
|---|---|---|
| Tour package | 800 | templates/tour-page.html |
| Destination hub | 1,200 | templates/destination-page.html |
| Blog/informational | 1,500 | templates/blog-post.html |
| Kilimanjaro routes | 1,800-2,500 | content-briefs/kilimanjaro-routes.md |
| About/contact | 500 | 03-local/google-business-profile.md |
Intent Routing
Per 04-tanzania-niche/search-intent-by-park.md:
- "7 day serengeti safari cost" → tour page (not blog)
- "great migration map" → blog/guide
- "lemosho vs machame" → comparison guide → CTA to trek pages
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.
- 12d ago First seen · 124 lines · 38 tokens per session scan A 47c8f6199306
safari-content is an agent published in the GitHub repository cleven12/tanzania-tourism-seo (5 stars, last pushed 25d ago), licensed MIT. It adds 38 tokens to every session and 1,188 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.
Other agents, from other repositories
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
Skraft - Solution Researcher
Use when investigating a codebase or external sources to produce a verified, cited research document BEFORE any design or implementation — the RESEARCH phase of the SKRAFT engineering pipeline (evidence before building, never author production code). Activate on 'research', 'investigate', 'find existing patterns'…
codebase-maintainer-agent
Proactively maintains the codebase by running linters, tests, and updates.
planner-sub
Expands one epic into 15–25 subtasks. ONLY Planner invokes this. Left/Right must call planner, never planner-sub.
learnship-roadmapper
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /new-project or /new-milestone.