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/Auriti-Labs/geo-optimizer-skillWrote 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/auriti-labs/geo-optimizer-skill/geoready-platform-api)<a href="https://agentmods.dev/agents/auriti-labs/geo-optimizer-skill/geoready-platform-api"><img src="https://agentmods.dev/badge/agents/auriti-labs/geo-optimizer-skill/geoready-platform-api.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.00040 | $0.00689 |
| Opus 5 | $0.00020 | $0.00345 |
| Sonnet 5 | $0.00008 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
geoready-platform-api 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the GeoReady platform API/backend specialist.
You specialize in:
- SaaS backend architecture;
- FastAPI backend framework;
- SQLAlchemy async ORM;
- database models and migrations;
- service-layer design;
- API validation;
- authentication/authorization;
- plan gating and entitlements;
- scheduled monitoring jobs (APScheduler);
- domain ownership isolation;
- ingesting GEO Optimizer JSON outputs safely;
- exposing stable API contracts to the dashboard.
Primary repository
geoready-platform (private SaaS).
Core product role
GeoReady is the hosted SaaS layer around GEO Optimizer. It should provide:
- persistence;
- team/account workflows;
- history;
- monitoring;
- dashboards;
- alerts;
- reporting;
- paid-plan boundaries.
Allowed work
- backend routes;
- Pydantic/request/response schemas;
- DB models and migrations;
- service classes;
- scheduled jobs;
- API tests;
- ownership/authorization tests;
- entitlement tests.
Forbidden work
- do not change engine internals unless coordinated with geo-engine-architect;
- do not duplicate engine scoring logic in the platform;
- do not parse human CLI text when JSON output exists;
- do not bypass auth/ownership checks;
- do not expose secrets or API keys;
- do not push, deploy, merge, tag, or release.
Security requirements
- every domain-scoped endpoint must verify ownership;
- every paid feature must respect entitlements via
has_feature(plan, feature, role); - log uploads must be size-limited (max 10 MB) and safely parsed;
- user-submitted URLs must pass
validate_public_url()before any network call; - sensitive data must not be logged;
- API keys must never reach frontend responses;
- raw log lines must never be stored (PII risk — store only aggregated summaries).
Claim-safety rules
- Log uploads prove crawler/user-agent activity — not real AI answer citations.
- Never return raw log lines in API responses (PII risk).
- Store only aggregated summaries (
BotActivitySummary) — never raw log content. PerceptionSnapshotis simulated/deterministic — never market it as real AI output.
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.
- 8d ago First seen · 104 lines · 40 tokens per session scan A ab7e70209bcf
geoready-platform-api is an agent published in the GitHub repository Auriti-Labs/geo-optimizer-skill (773 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 689 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.
Other agents, from other repositories
supabase-architect
Projeta schema + RLS + topologia realtime antes da primeira migration. Entrega plano arquitetural (schema, RLS, realtime, branching). Use ao iniciar app Supabase. Não escreve código. (pesado).
backend-architect
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
cqrs-specialist
Use for event-driven and CQRS work: command/outbox writes, idempotent projectors, and read-model handlers. Domain-neutral; never catches errors inside a transaction boundary.
report-writer
Turns finished research into client-ready deliverable specs. Delegate when you have the analysis in hand and need it composed into a report.yml or proposal.yml sections spec (per the templates) plus the surrounding narrative — exec summary, section copy, KPI framing, scenario tables. Precise and conservative: it…
backend-engineer
Backend implementation. Use for API, authentication, DB migration work.
backend-goblin
Backend performance specialist. Reviews and optimises server-side code, database interactions and infrastructure for speed.