beeweave copilot-instructions.md

Project instructions for BeeWeave, a Python command-line workbench that collects source material, turns it into reusable knowledge, and uses that knowledge as future context.

In plain words
What is it for?
Use them when developing or maintaining the BeeWeave CLI, its bundled skills, workspace setup, knowledge base, or browser extension.
Why use it?
They explain where drafts, the compiled knowledge base, skills, setup templates, and browser-capture files belong.

Instructions file for GitHub Copilot

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/ptonlix/beeweave/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/ptonlix/beeweave

Made for: GitHub Copilot.

Per session 1,354 This file is loaded in full into every session.
When invoked 1,354 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.01354 $0.01354
Opus 5 $0.00677 $0.00677
Sonnet 5 $0.00271 $0.00271
Haiku 4.5 $0.00135 $0.00135

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

Security

Grade A, and why

beeweave 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 3d 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 · 163 lines

How it starts

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

BeeWeave — Copilot Context

BeeWeave is an agent-native creation workbench for building a creative data flywheel: collect source material, create with agents, distill durable knowledge, reuse that knowledge as context, then collect better material for the next loop.

This repository contains the Python CLI, bundled skills, bootstrap templates, browser extension assets, tests, and documentation used to install and maintain BeeWeave workspaces.

Project Overview

  • Purpose: Help agents and humans move material through a structured loop: collect -> create -> distill -> reuse context -> collect better.
  • Runtime model: workbench/ is the staging and drafting area; vault/ is the compiled markdown knowledge base.
  • CLI: The public console command is bwe.
  • Package: Python package code lives under beeweave/; package metadata and the CLI entrypoint live in pyproject.toml.
  • Skills: Source skills live under .skills/wiki/ and .skills/workbench/. Each skill folder uses a SKILL.md workflow file.
  • Bootstrap: Agent-facing setup templates live under bootstrap/.
  • Extension: Browser capture assets live under extensions/brain-capture/.

Key Concepts

  • BeeWeave is a loop, not a one-way archive.
  • Raw inputs, drafts, captures, web clips, and source libraries belong in workbench/.
  • Stable reusable knowledge belongs in vault/ as markdown with metadata and Obsidian-style [[wikilinks]].
  • The vault is a compiled artifact: concepts, entities, references, project notes, synthesis pages, and graph-ready relationships distilled from higher signal material.
  • Setup-generated runtime vault/ and workbench/ directories should not be committed to this repository.

Runtime Layout

BeeWeave setup creates this structure inside a user-selected workspace:

project/
+-- vault/                  # durable markdown knowledge
|   +-- concepts/
|   +-- entities/
|   +-- skills/
|   +-- references/
|   +-- synthesis/
|   +-- projects/
|   +-- _meta/
|   +-- _archives/
|   +-- _staging/
|   +-- .obsidian/
+-- workbench/              # staging and drafting area
    +-- inbox/
    |   +-- captures/
    |   +-- web/
    |   +-- archived/
    |   +-- rejected/
    +-- articles/
    |   +-- drafts/
    |   +-- published/
    +-- library/

Read the full file on GitHub · 163 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. 3d ago First seen · 163 lines · 1,354 tokens per session scan A dbb204a9a49a

Subscribe to this mod's changes

beeweave copilot-instructions.md is an instructions file published in the GitHub repository ptonlix/beeweave (6 stars, last pushed 1mo ago), licensed MIT. It adds 1,354 tokens to every session, about $0.0068 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-31.

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