vibeauracle copilot-instructions.md

vibeauracle copilot-instructions.md is an instructions file for GitHub Copilot from nathfavour/vibeauracle. It costs 328 tokens per session, scanned A, original, MIT.

Repository-specific instructions for GitHub Copilot when working on Vibeauracle, a Go workspace with a terminal user interface and supporting modules.

In plain words
What is it for?
Use them when planning, changing, testing, or documenting code in the Vibeauracle repository.
Why use it?
They give the agent the project's structure, preferred commands, testing expectations, and hardware-related constraints to follow.

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

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 vibeauracle copilot-instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/nathfavour/vibeauracle/copilot-instructions.svg)](https://agentmods.dev/instructions/nathfavour/vibeauracle/copilot-instructions)
Your own site
<a href="https://agentmods.dev/instructions/nathfavour/vibeauracle/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/nathfavour/vibeauracle/copilot-instructions.svg" alt="Measured on agentmods" height="20"></a>
Per session 328 This file is loaded in full into every session.
When invoked 328 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.00328 $0.00328
Opus 5 $0.00164 $0.00164
Sonnet 5 $0.00066 $0.00066
Haiku 4.5 $0.00033 $0.00033

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

Security

Grade A, and why

vibeauracle 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 · 14 lines

What it actually says

GitHub Copilot instructions for vibeauracle

vibeauracle is a distributed, system-intimate AI engineering ecosystem built as a Go workspace with a Bubble Tea CLI (cmd/vibeaura), a cognitive internal/brain, and supporting modules for model providers, tools, system monitoring, and extensions. The Copilot agent should treat the repo as a cohesive whole: plan-change-verify via the brain's Plan-Execute-Reflect loop, respect the modular boundaries, and keep the TUI-first workflow and tooling integrations in mind.

What to prioritize

  • Learn and honor the Hexagonal / Go workspace structure: go.work governs the modules, and each package has a distinct responsibility (brain, sys, context, model, etc.).
  • Favor vibeaura commands and Go tooling for tasks; when in doubt, prefer go test ./... scoped to the touched module, run go work sync if dependencies change, and mention vibeaura helpers when describing behavior.
  • Document discoveries via README/ARCHITECTURE cues; link to docs/, VIBES.md, and FLOW.txt when relevant.

Style & guardrails

  • Keep explanations concise, structured, and system-aware. Mention hardware-awareness expectations (e.g., Termux, Arch focus) when they influence decisions.
  • Do not assume external systems beyond the repo; rely on the provided vector/KV store conventions and keep secrets out of outputs.
  • Encourage users to test with module-specific go test commands and reiterate the cognitive loop when proposing multi-step solutions.
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 · 14 lines · 328 tokens per session scan A e79638444325

Subscribe to this mod's changes

vibeauracle copilot-instructions.md is an instructions file published in the GitHub repository nathfavour/vibeauracle (5 stars, last pushed 2mo ago), licensed MIT. It adds 328 tokens to every session, about $0.0016 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.