What is shine copilot-instructions.md?

Project instructions for Shine, a Rust command-line application organized as a Cargo workspace. They describe how to build, run, test, format, lint, and check the project.

Use them when working on Shine's Rust code, including running the command-line tool, testing one feature, or checking the full project before a commit.

They give a coding agent the repository's expected commands and checks, reducing guesswork before changes are committed.

shine copilot-instructions.md — Instructions file by biulight

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/biulight/shine/copilot-instructions

Clone the repo

git clone --depth 1 https://github.com/biulight/shine

Made for: GitHub Copilot.

Per session 1,202 This file is loaded in full into every session.

When invoked 1,202 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.

Model	Per session	Once invoked
Fable 5	$0.01202	$0.01202
Opus 5	$0.00601	$0.00601
Sonnet 5	$0.00240	$0.00240
Haiku 4.5	$0.00120	$0.00120

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

Security

Grade A, and why

shine 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 · 113 lines

How it starts

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

Copilot Instructions

Build, Test & Lint

# Build
cargo build
cargo build --release          # binary at target/release/shine

# Run (dev)
cargo run -- shell list
cargo run -- shell install proxy
cargo run -- shell uninstall --dry-run

# Test
cargo nextest run --all-features   # used by pre-commit
cargo test                         # fallback without nextest

# Single test
cargo nextest run -E 'test(install_then_uninstall)'
cargo test shells::tests::install_then_uninstall_roundtrip

# Lint / format
cargo fmt
cargo clippy --all-targets --all-features --tests --benches -- -D warnings
cargo deny check bans licenses sources
typos

Pre-commit runs all of the above on every commit. All must pass before committing.

Architecture

Cargo workspace with two publishable crates:

shine-cli (workspace root; sources in cli/) — the shine binary (Clap-based, async with Tokio)
shine-core (utils/) — UI-agnostic shared library with utils::migration::sync_table, a TOML comment-preserving table updater

Preset files under the workspace-root presets/ directory are compiled into the binary via rust_embed (PresetAssets in cli/src/presets.rs). cli/build.rs registers cargo:rerun-if-changed=presets so cargo re-embeds when preset files change.

Command routing

main.rs → Commands enum → module handlers:

Top-level command	Handler module
`shell list/install/uninstall`	`cli/src/shells/`
`app list/install/uninstall`	`cli/src/apps/`
`update` / `upgrade`	`cli/src/update_check.rs`
`check`	`cli/src/check.rs`

Shell preset install flow

presets::extract_prefix("shell[/category]", presets_dir) — unpacks embedded .sh files to ~/.shine/presets/shell/, sets executable bit
bin_links::link_executables(bin_dir, sources) — creates flat symlinks in ~/.shine/bin/
shells::append_path_to_shell_config — appends a sentinel-guarded export PATH block to ~/.zshrc (or equivalent); Fish uses fish_add_path

Read the full file on GitHub · 113 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.

2d ago First seen · 113 lines · 1,202 tokens per session scan A 9298680906c6

Subscribe to this mod's changes

shine copilot-instructions.md is an instructions file published in the GitHub repository biulight/shine (5 stars, last pushed 2d ago), licensed MIT. It adds 1,202 tokens to every session, about $0.0060 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.

Code review Git and workflow Testing

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

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

shine copilot-instructions.md