agentmods.dev

CODEBUDDY

CODEBUDDY is an agent for Claude Code from loki-ai-ch/spec-manager. It costs 0 tokens per session (524 once invoked), scanned A, a copy of CLAUDE, MIT.

A project instruction for CodeBuddy that tells it to use spec-manager, a tool for planning and approving work before implementation.

In plain words
What is it for?
It helps CodeBuddy create and follow staged specifications, inspect existing decisions, link tasks to approved plans, and record verification evidence.
Why use it?
It gives CodeBuddy a consistent process for handling new or substantial changes and helps prevent unapproved code edits.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

not rated 5repo 3mo ago A scan 0 tokens copy · 88% MIT

Good fit It helps CodeBuddy create and follow staged specifications, inspect existing decisions, link tasks to approved plans, and record verification evidence.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/loki-ai-ch/spec-manager/codebuddy
View source ↗ loki-ai-ch/spec-manager npmjs.com
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.

Clone the repo
git clone --depth 1 https://github.com/loki-ai-ch/spec-manager

Made for: Claude Code.

Wrote 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.

agentmods badge for CODEBUDDY

README.md
[![agentmods](https://agentmods.dev/badge/agents/loki-ai-ch/spec-manager/codebuddy/github.svg)](https://agentmods.dev/agents/loki-ai-ch/spec-manager/codebuddy)
Your own site
<a href="https://agentmods.dev/agents/loki-ai-ch/spec-manager/codebuddy"><img src="https://agentmods.dev/badge/agents/loki-ai-ch/spec-manager/codebuddy/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.

agentmods 80×15 button for CODEBUDDY

Your own site · 80×15
<a href="https://agentmods.dev/agents/loki-ai-ch/spec-manager/codebuddy"><img src="https://agentmods.dev/badge/agents/loki-ai-ch/spec-manager/codebuddy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 524 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 88% copy Near-identical to another mod 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.1 $0.00000 $0.00524
Opus 5.5 $0.00000 $0.00210
Sonnet 5.5 $0.00000 $0.00105
Haiku 4.5 $0.00000 $0.00052

Measured 1mo ago against content hash e3a3c049fbc8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

CODEBUDDY 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 1mo 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.

Origin

This is a copy

88% identical to CLAUDE — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/spec-manager/templates/agents/CODEBUDDY.md · 28 lines

How it starts

The opening of the file, as written. The whole thing — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spec-Driven Development

This project uses spec-manager for local-first spec-driven development. CodeBuddy should use the project skill at .codebuddy/skills/spec-manager/ when the user asks for /spec-manager or asks to follow the spec-manager workflow.

Unified Rules

  • Feature work MUST go through spec-manager.
  • New or non-trivial work follows L1 -> L2 -> L3 -> Agent Task.
  • Never write implementation code without a frozen L3 spec.
  • L1/L2 approval advances draft -> confirmed; one explicit L3 approval (an explicit user approval) advances draft -> frozen.
  • Before creating a new spec, inspect existing specs and decisions.
  • Before code edits, read the frozen L3 spec and create/start an Agent Task.
  • planJson coveredSpecs MUST include the current L3 specCode.
  • If adaptive workflow is enabled, Task creation records a standard or governed Profile snapshot; governed requires the frozen L3 to declare ## 关键验收标准 with valid AC IDs, and task complete requires successful verification evidence covering every critical AC. standard reports missing coverage as warnings. Use spec-manager project profile recommend --request "<work>" for a deterministic, explainable recommendation; it does not auto-enable adaptive workflow and is not a hidden gate. Use spec-manager project profile metrics [--topic <topic>] [--json] for a read-only governance report over Profile adoption, governed coverage gaps, standard warnings, and explicit overrides; metrics does not modify config or historical Tasks. Use spec-manager project readiness critical [--topic <topic>] [--json] for a read-only critical AC readiness report and repair suggestions; it must not auto-generate or insert critical AC. Before enabling adaptive workflow, use spec-manager project workflow preview [--json] for a read-only adoption preview; preview does not write config, migrate historical Tasks, or act as an enable gate.
  • quick remains a restricted lightweight exception and does not create the full L1/L2/L3/Task chain.
  • Validate L3 markdown plans with spec-manager spec validate-plan --from-spec <L3-code>.
  • Record execution with spec-manager task step; finish with spec-manager task complete.

Read the full file on GitHub · 28 lines

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. 1mo ago First seen · 28 lines · 0 tokens per session scan A e3a3c049fbc8

Subscribe to this mod's changes

CODEBUDDY is an agent published in the GitHub repository loki-ai-ch/spec-manager (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 524 tokens. A static security scan graded it A with 0 findings. It is 88% identical to CLAUDE, differing in 16 lines, and is treated as a copy.

Building agentsPlanningai-agentsai-codingcli-toolharnesssddspec-driven-development
Related

Other agents, from other repositories

planner

Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.

joanseg/specmanager · 46 tokens

reviewer

Read-only spec-compliance reviewer. Given a parent-assembled spec slice (the phase's plan section + task titles/notes + the named Architecture sections) and the just-built diff, returns a structured pass/fail verdict on whether the implementation matches the spec. Never writes. Invoked by /specmanager-build after the…

joanseg/specmanager · 79 tokens

ops-infra-code

Infrastructure as Code (Terraform, OpenTofu). Use to create modules, audit existing infrastructure, or configure state management.

christopherlouet/claude-base · 29 tokens

doc-onboard

Discovery and understanding of a codebase. Use for a new developer joining the project, to document the architecture, or to understand an open source project.

christopherlouet/claude-base · 34 tokens

dev-document

Code that generates documents inside an application (PDF, DOCX, XLSX, PPTX). Use to add an export, an invoice or a report generator to an app. For Claude to write or edit an office file itself, Anthropic's docx/pdf/xlsx/pptx skills fit better.

christopherlouet/claude-base · 64 tokens

legal-payment

Compliant payment integration (Stripe, PayPal). Use to implement payments in compliance with PCI-DSS and regulations.

christopherlouet/claude-base · 26 tokens