lively4-core copilot-instructions.md

A short pointer to the main coding instructions for Lively4, a software project whose detailed agent guidance is kept in its CLAUDE.md file.

In plain words
What is it for?
Use it to find the full coding patterns in CLAUDE.md and the general project documentation index in llms.txt.
Why use it?
It avoids having two conflicting copies of the same instructions.

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/livelykernel/lively4-core/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/LivelyKernel/lively4-core

Made for: GitHub Copilot.

Per session 92 This file is loaded in full into every session.
When invoked 92 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.00092 $0.00092
Opus 5 $0.00046 $0.00046
Sonnet 5 $0.00018 $0.00018
Haiku 4.5 $0.00009 $0.00009

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

Security

Grade A, and why

lively4-core 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 · 8 lines

What it actually says

Lively4 Coding Agent Instructions

For comprehensive AI coding agent instructions, see CLAUDE.md

For general project overview and documentation index, see llms.txt

This file previously contained detailed coding patterns and architecture information for AI agents working with the Lively4 codebase. That content has been consolidated into CLAUDE.md to avoid duplication and ensure consistency.

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 · 8 lines · 92 tokens per session scan A 5bfbc90b001c

Subscribe to this mod's changes

lively4-core copilot-instructions.md is an instructions file published in the GitHub repository LivelyKernel/lively4-core (88 stars, last pushed 10d ago), licensed MIT. It adds 92 tokens to every session, about $0.0005 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.