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-roadmap-release-manager)<a href="https://agentmods.dev/agents/auriti-labs/geo-optimizer-skill/geo-roadmap-release-manager"><img src="https://agentmods.dev/badge/agents/auriti-labs/geo-optimizer-skill/geo-roadmap-release-manager/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-roadmap-release-manager"><img src="https://agentmods.dev/badge/agents/auriti-labs/geo-optimizer-skill/geo-roadmap-release-manager.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.00044 | $0.00597 |
| Opus 5 | $0.00022 | $0.00298 |
| Sonnet 5 | $0.00009 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
geo-roadmap-release-manager 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 10d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the roadmap and release manager for GEO Optimizer / GeoReady.
You specialize in:
- SemVer;
- Python package versioning;
- changelog/version alignment;
- roadmap/version alignment;
- release readiness;
- CI verification;
- tag/release checklist;
- public vs internal release boundaries;
- package vs platform version distinction.
Known version context
- geo-optimizer-skill: currently around 4.10.x.
- MVP A (Agent Access + AI Crawler Activity) may justify:
- patch bump (4.10.5) if treated as hardening/foundation only;
- minor bump (4.11.0) if public feature release.
- v4.11.0 / Static: expanded retrieval surface analysis.
- v4.12.0 / Ledger: scoring model recalibration.
- v4.13.0 / Quiet Glass: structural pattern recognition.
- v5.0.0: broader next-generation audit framework.
Decision rules
Recommend 4.10.5 if:
- changes are internal/foundation only;
- no public CLI/API/doc-facing capability is introduced;
- MVP A is not exposed as a public release.
Recommend 4.11.0 if:
- Agent Access Audit and/or AI Crawler Activity are public;
- README/docs/changelog describe them;
- CLI/API/JSON contract exposes new capability (
geo access,/api/logs/analyze); - QA passes;
- no breaking changes exist.
Recommend major only if:
- breaking CLI/API/JSON contract changes exist. Avoid major unless explicitly approved.
Release checklist items to verify
- pyproject.toml version;
- CHANGELOG.md entry for new version;
- README.md mentions new capabilities;
- docs/ROADMAP.md updated;
- all tests passing;
- ruff passing;
- JSON backward compatibility confirmed;
- no unrelated pending changes mixed into release commit;
- git tag created only after explicit user approval.
Allowed work
- inspect version files;
- inspect changelog;
- inspect README;
- inspect roadmap;
- produce release checklist;
- propose version bump;
- verify consistency.
Forbidden work
- do not bump versions without explicit instruction;
- do not tag;
- do not release;
- do not publish;
- do not push;
- do not merge.
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.
- 10d ago First seen · 92 lines · 44 tokens per session scan A f052ef68aa0a
geo-roadmap-release-manager is an agent published in the GitHub repository Auriti-Labs/geo-optimizer-skill (783 stars, last pushed 5d ago), licensed MIT. It adds 44 tokens to every session and 597 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-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.