agentmods.dev

codedb copilot-instructions.md

Project-specific instructions for codedb, a Zig code-intelligence server that helps tools understand source code.

In plain words
What is it for?
Use them when working on codedb, especially to run its Zig tests, file issues with failing tests, and follow its cleanup and test-style requirements.
Why use it?
They give coding agents the project's required build, test, issue-reporting, branching, and test-writing rules.

Instructions file for GitHub Copilot

1.4k 2d ago A scan 385 tokens original BSD-3-Clause
View the source file justrach/codedb
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 instructions/justrach/codedb/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/justrach/codedb

Made for: GitHub Copilot.

Per session 385 This file is loaded in full into every session.
When invoked 385 The same file — it is already loaded in full.
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.00385 $0.00385
Opus 5 $0.00192 $0.00192
Sonnet 5 $0.00077 $0.00077
Haiku 4.5 $0.00038 $0.00038

Measured 2d ago against content hash fc6506187e50, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

codedb copilot-instructions.md 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 2d 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.

.github/copilot-instructions.md · 39 lines

What it actually says

codedb — Agent Instructions

Project

Zig 0.17.0-dev code intelligence server (pinned to 0.17.0-dev.813+2153f8143). Tests live in src/test_*.zig. Build and test with zig build test.

Rules

Filing Issues

Every GitHub issue must include a failing test case. No exceptions.

When creating an issue:

  1. Write a test "issue-XX: <description>" block in src/tests.zig that fails on the current main branch
  2. Verify it fails: zig build test 2>&1 | grep "issue-XX"
  3. File the issue via gh issue create with this structure:
    • Title: <module>: <concise description>
    • Body sections: Problem, Failing Test (the zig test block), Expected, Fix
    • Labels: bug for defects, priority:p0 for crashes, priority:p2 for correctness
  4. Commit the failing test on a branch: issue-XX-failing-test
  5. Do not fix the bug in the same commit as the failing test

If you cannot write a failing test, the issue is not well-defined enough to file.

Test Style

  • Use std.testing and testing.allocator
  • Use std.heap.ArenaAllocator for Explorer tests
  • Always defer cleanup (arena.deinit, allocator.free)
  • One test per issue, named test "issue-XX: <short description>"
  • Keep tests minimal — only exercise the specific broken code path

Code Style

  • No comments or documentation changes unless explicitly asked
  • Prefer minimal, targeted fixes over refactors
  • Follow existing patterns in the module you're editing
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. 2d ago First seen · 39 lines · 385 tokens per session scan A fc6506187e50

Subscribe to this mod's changes

codedb copilot-instructions.md is an instructions file published in the GitHub repository justrach/codedb (1,371 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 385 tokens to every session, about $0.0019 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.

PlanningTestingagentic-aiagentsanthropiccursorgeminimcp
Related

Other instructions, from other repositories

capsule CLAUDE.md

Instructions for endorhq/capsule, covering claude.md, project overview, tech stack, commands and web app (packages/web).

endorhq/capsule · 2,665 tokens

gmail-mcp GEMINI.md

Gemini CLI instructions for hahaha-saygex/gmail-mcp, covering gmail mcp guidelines for gemini, available operations, email operations (9), label management (5) and filter management (5).

hahaha-saygex/gmail-mcp · 1,770 tokens

gmail-mcp CLAUDE.md

Claude Code instructions for hahaha-saygex/gmail-mcp, covering gmail mcp guidelines for claude, available operations, email operations (10), label management (5) and filter management (5).

hahaha-saygex/gmail-mcp · 1,797 tokens

hindsight CLAUDE.md

Instructions for vectorize-io/hindsight, covering claude.md, project overview, development commands, local development (api + ui) and start both api server and control plane ui.

vectorize-io/hindsight · 4,846 tokens

claude-code-settings copilot-instructions.md

Instructions for feiskyer/claude-code-settings, covering claude.md, environment setup, required dependencies, configuration and skills.

feiskyer/claude-code-settings · 649 tokens

goodboy AGENTS.md

Instructions for akhayam99/goodboy, covering agents.md, where new code goes, naming, components and exports and store selectors and memoization.

akhayam99/goodboy · 1,263 tokens