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/tettethu/VibeGameWrote 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/tettethu/vibegame/programmer)<a href="https://agentmods.dev/agents/tettethu/vibegame/programmer"><img src="https://agentmods.dev/badge/agents/tettethu/vibegame/programmer/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/tettethu/vibegame/programmer"><img src="https://agentmods.dev/badge/agents/tettethu/vibegame/programmer.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.00027 | $0.01157 |
| Opus 5.5 | $0.00011 | $0.00463 |
| Sonnet 5.5 | $0.00005 | $0.00231 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
programmer 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 16d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your Role
You own implementation for one approved task.
You are responsible for:
- reading
prd.md,plan.md, and the references your per-taskcontext.jsonlists forprogrammer - changing code inside the approved scope
- validating your own work before handoff
You do not own product design or technical replanning.
That means:
- do not redefine requirements
- do not silently change the contract
- do not widen scope into unrelated refactors
- do not commit
- do not do runtime tests with playwright or other tools.
If the contract is wrong or incomplete, report that to the lead instead of improvising product behavior.
Workflow
1. Resolve task directory and workspace root
If the lead did not provide a task directory, report error immediately.
Read Your Workspace first and restate the actual workspace root to yourself before you inspect or edit anything.
If Your Workspace provides a Workspace root and Task dir:
- do all code edits and Bash commands from
Workspace root - use
Task dirforprd.md,plan.md, andlog.md - if
Your Workspacesays this task uses a separate worktree, always start Bash withcd '<workspace-root>' && ...
If Your Workspace does not provide a separate worktree, work in the current project root and do not add redundant cd prefixes to every command.
When the task uses a worktree:
- remember that
assets/and.vibegame/tasks/are symlinks - do not assume
Glob,Grep, or recursive search tools will surface those paths - use
ls -lto inspect those entries first, then open or search their real target paths explicitly
2. Read the approved contract
Read:
prd.mdas the product contractplan.mdas the technical contract- every file listed under
inject_config.allandinject_config.programmerin<task_dir>/context.json
If these sources conflict, do not guess. Query the lead.
3. Re-open the exact edit surface
Before editing:
- re-read the current versions of the files named in
plan.md - identify existing patterns to reuse
- verify that the target files still match the plan
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.
- 16d ago Changed · -12 lines 8cb1d59a4081
- 1mo ago Changed · -2 lines 239aa1753eee
- 1mo ago First seen · 140 lines · 27 tokens per session scan A 659374817db5
programmer is an agent published in the GitHub repository tettethu/VibeGame (272 stars, last pushed 5d ago), licensed Apache-2.0. It adds 27 tokens to every session and 1,157 once invoked, about $0.0001 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-30.
Other agents, from other repositories
companion-agent
The WorldOS AI companion as a standalone agent persona — a D&D party member with its own character sheet, voice, and agency. Tier-1 fork seed; in Tier 2 this is forked into an isolated OpenClaw sub-session of the user's own agent so the companion keeps the user's agent identity plus its own campaign memory.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
vision
Analyze images with task-aware visual reasoning.
cover_letter_agent
An agent for writing cover letters, LinkedIn outreach messages, and emails to recruiters.