agentmods.dev

opencode-agent-skills copilot-instructions.md

opencode-agent-skills copilot-instructions.md is an instructions file for GitHub Copilot from joshuadavidthomas/opencode-agent-skills. It costs 681 tokens per session, scanned A, original, MIT.

Repository instructions for AI coding agents working on a project that uses bd, a Git-backed issue tracker called Beads. They describe how to find, create, update, close, and synchronize development tasks, along with project commands.

In plain words
What is it for?
Use them when contributing to the project, especially to select available issues, claim work, record progress, run validation commands, and synchronize completed tasks.
Why use it?
They give coding agents a consistent way to manage work and keep task status synchronized with the repository. They also document the commands used to build, test, lint, and check the project.

Instructions file for GitHub Copilot

not rated 271 9d ago A scan 681 tokens original MIT
View the source file joshuadavidthomas/opencode-agent-skills
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/joshuadavidthomas/opencode-agent-skills/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/joshuadavidthomas/opencode-agent-skills

Made for: GitHub Copilot.

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 opencode-agent-skills copilot-instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/joshuadavidthomas/opencode-agent-skills/copilot-instructions.svg)](https://agentmods.dev/instructions/joshuadavidthomas/opencode-agent-skills/copilot-instructions)
Your own site
<a href="https://agentmods.dev/instructions/joshuadavidthomas/opencode-agent-skills/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/joshuadavidthomas/opencode-agent-skills/copilot-instructions.svg" alt="Measured on agentmods" height="20"></a>
Per session 681 This file is loaded in full into every session.
When invoked 681 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.00681 $0.00681
Opus 5 $0.00341 $0.00341
Sonnet 5 $0.00136 $0.00136
Haiku 4.5 $0.00068 $0.00068

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

Security

Grade A, and why

opencode-agent-skills 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 4d 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 · 79 lines

How it starts

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

GitHub Copilot Instructions

Issue Tracking with bd

This project uses bd (beads) for issue tracking - a Git-backed tracker designed for AI-supervised coding workflows.

Key Features:

  • Dependency-aware issue tracking
  • Auto-sync with Git via JSONL
  • AI-optimized CLI with JSON output
  • Built-in daemon for background operations
  • MCP server integration for Claude and other AI assistants

CRITICAL: Use bd for ALL task tracking. Do NOT create markdown TODO lists.

Essential Commands

# Find work
bd ready --json                    # Unblocked issues
bd stale --days 30 --json          # Forgotten issues

# Create and manage
bd create "Title" -t bug|feature|task -p 0-4 --json
bd create "Subtask" --parent <epic-id> --json  # Hierarchical subtask
bd update <id> --status in_progress --json
bd close <id> --reason "Done" --json

# Search
bd list --status open --priority 1 --json
bd show <id> --json

# Sync (CRITICAL at end of session!)
bd sync  # Force immediate export/commit/push

Workflow

  1. Check ready work: bd ready --json
  2. Claim task: bd update <id> --status in_progress
  3. Work on it: Implement, test, document
  4. Discover new work? bd create \"Found bug\" -p 1 --deps discovered-from:<parent-id> --json
  5. Complete: bd close <id> --reason \"Done\" --json
  6. Sync: bd sync (flushes changes to git immediately)

Priorities

  • 0 - Critical (security, data loss, broken builds)
  • 1 - High (major features, important bugs)
  • 2 - Medium (default, nice-to-have)
  • 3 - Low (polish, optimization)
  • 4 - Backlog (future ideas)

Git Workflow

  • Always commit .beads/issues.jsonl with code changes
  • Run bd sync at end of work sessions
  • Install git hooks: bd hooks install (ensures DB ↔ JSONL consistency)

MCP Server (Recommended)

For MCP-compatible clients (Claude Desktop, etc.), install the beads MCP server:

  • Install: pip install beads-mcp
  • Functions: mcp__beads__ready(), mcp__beads__create(), etc.

Read the full file on GitHub · 79 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. 4d ago First seen · 79 lines · 681 tokens per session scan A e2cf0fe0f943

Subscribe to this mod's changes

opencode-agent-skills copilot-instructions.md is an instructions file published in the GitHub repository joshuadavidthomas/opencode-agent-skills (271 stars, last pushed 9d ago), licensed MIT. It adds 681 tokens to every session, about $0.0034 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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens