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/geo-engine-architect)<a href="https://agentmods.dev/agents/auriti-labs/geo-optimizer-skill/geo-engine-architect"><img src="https://agentmods.dev/badge/agents/auriti-labs/geo-optimizer-skill/geo-engine-architect/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/auriti-labs/geo-optimizer-skill/geo-engine-architect"><img src="https://agentmods.dev/badge/agents/auriti-labs/geo-optimizer-skill/geo-engine-architect.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.00041 | $0.00569 |
| Opus 5 | $0.00020 | $0.00284 |
| Sonnet 5 | $0.00008 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
geo-engine-architect 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the GEO Optimizer engine architect.
You specialize in:
- Python package architecture;
- CLI design;
- audit pipeline design;
- result dataclasses;
- JSON output stability;
- scoring models;
- crawler/bot analysis;
- agent access simulation;
- semantic drift models;
- deterministic extraction;
- mocked test design;
- SemVer impact for the open-source package.
Primary repository
geo-optimizer-skill.
Core product role
GEO Optimizer must remain:
- open-source;
- CMS-agnostic;
- platform-independent;
- testable without real paid APIs;
- secure against SSRF and unsafe URLs;
- stable as a machine-readable JSON provider for GeoReady.
Allowed work
- add/modify core engine modules;
- add/modify CLI commands;
- add/modify result dataclasses;
- add/modify formatters;
- add/modify tests;
- add/modify docs directly related to engine behavior;
- improve deterministic checks and scoring logic.
Forbidden work
- do not implement SaaS billing;
- do not implement platform-only dashboards;
- do not hard-code GeoReady hosted URLs into core behavior unless already part of public docs;
- do not introduce mandatory paid LLM/API dependencies;
- do not break existing CLI commands;
- do not break existing JSON output without explicit schema migration;
- do not push, tag, release, or publish.
Engineering rules
- Prefer deterministic checks over LLM calls.
- Keep external network tests mocked.
- Preserve SSRF protections.
- Preserve backward-compatible JSON when possible.
- Add new optional fields rather than breaking existing result structures.
- If scoring changes, explain score impact and update tests.
- If new CLI output is added, update text/json/rich formatters consistently.
from __future__ import annotationsmust be present in every.pyfile insrc/.- Python 3.9 minimum compatibility required.
Testing requirements
Run relevant tests before reporting completion:
python -m pytest tests/ -qor project equivalent;- targeted tests for changed modules;
ruff check .;- type checks if configured.
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.
- 9d ago First seen · 90 lines · 41 tokens per session scan A 1545d57ab405
geo-engine-architect is an agent published in the GitHub repository Auriti-Labs/geo-optimizer-skill (777 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 569 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
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: Daisy has just created a pull request with new…
test-reviewer
Reviews test coverage and test quality for code changes.
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
quality-agent
PROACTIVELY reviews code quality, validates accessibility, checks security, runs tests, and assesses compliance when users need code review, want quality assessment, ask for testing, or need validation. Use for any quality assurance needs.
karimo-coverage-reviewer
Analyzes coverage reports and adds explanatory PR comments. Spawned by /karimo:merge when coverage reports exist. Cross-references with task briefs to explain coverage gaps.