opencode

A set of instructions for using AgentLoopKit as the development workflow in a repository. It explains which guidance files and task records to read before editing and which checks to perform before finishing.

In plain words
What is it for?
It is for starting repository work, checking agent readiness, reviewing the whole change, avoiding destructive actions, and documenting files changed, tests, risks, and rollback notes.
Why use it?
It provides a repeatable way to prepare, make small changes, verify them, and report what changed, reducing overlooked instructions and untested work.

Agent

Install

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.

agentmods
npx agentmods add agents/abhiyoheswaran1/agentloopkit/opencode
Clone the repo
git clone --depth 1 https://github.com/abhiyoheswaran1/AgentLoopKit
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 209 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00209
Opus 5 $0.00000 $0.00105
Sonnet 5 $0.00000 $0.00042
Haiku 4.5 $0.00000 $0.00021

Measured yesterday against content hash 25208e0f1620, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

opencode 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 yesterday.

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.

.agentloop/agents/opencode.md · 21 lines

What it actually says

OpenCode Agent Instructions

Use AgentLoopKit as the working loop for this repository.

Before editing:

  • Read AGENTS.md.
  • Read AGENTLOOP.md.
  • Check .agentloop/tasks/.
  • Run agentloop doctor --redact-paths before Start when you need to confirm agent-readiness guidance is current.
  • Before broad file reads or long-session continuation, use one preflight: call MCP tool agentloop_start when MCP tools are configured; otherwise run agentloop start --for generic --goal implement --redact-paths. Use agentloop context handles to list available handles, then agentloop context show <handle> to expand local source truth only when needed and avoid broad repo reads.

Rules:

  • Do not take destructive actions without explicit approval.
  • Prefer small diffs.
  • Verify before completion.
  • Summarize changed files, tests, risks, and rollback notes.

If OpenCode config conventions differ in your setup, paste or link this file into the appropriate agent instructions.

Changes

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.

  1. yesterday First seen · 21 lines · 0 tokens per session scan A 25208e0f1620

Subscribe to this mod's changes

opencode is an agent published in the GitHub repository abhiyoheswaran1/AgentLoopKit (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 209 tokens. 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.

Related

Other agents, from other repositories

Jump Start: Analyst

Phase 1 agent focused on user research, personas, journeys, and value proposition development.

CGSOG-JumpStarts/JumpStart-AutoNav · 22 tokens

Jump Start: Architect

Phase 3 agent responsible for translating the PRD into a technical blueprint and an ordered implementation plan. This includes technology selection, component design, data modeling, API specification, and documenting architectural decisions.

CGSOG-JumpStarts/JumpStart-AutoNav · 44 tokens

developer

You are The Developer, the Phase 4 agent in the Jump Start framework. Your role is to execute the implementation plan produced by the Architect, writing code that faithfully implements the specifications. You are methodical, test-driven, and disciplined. You follow the plan, write clean code, and verify your work…

CGSOG-JumpStarts/JumpStart-AutoNav · 0 tokens

Jump Start: Product Manager

Phase 2 -- Translate the product concept into a detailed, unambiguous Product Requirements Document (PRD) with user stories, acceptance criteria, and prioritization.

CGSOG-JumpStarts/JumpStart-AutoNav · 38 tokens

challenger

You are The Challenger, the Phase 0 agent in the Jump Start framework. Your role is to rigorously interrogate the human's initial idea, assumption, or problem statement before any product thinking, planning, or building begins.

CGSOG-JumpStarts/JumpStart-AutoNav · 0 tokens

Jump Start: Developer

Phase 4 -- Execute the implementation plan task by task, writing tested code.

CGSOG-JumpStarts/JumpStart-AutoNav · 20 tokens