SquidC5 copilot-instructions.md

GitHub Copilot instructions for SquidC5, a security-focused command-and-control team server for authorized red-team and penetration tests. They define project rules for safe operation and consistent command-line work.

In plain words
What is it for?
Working on the SquidC5 codebase, keeping its operator command-line interface and documentation aligned, and handling Docker or production deployment safely.
Why use it?
They keep security boundaries, tool restrictions, secrets, documentation, and deployment practices from being weakened accidentally.

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/squidsec/squidc5/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/SquidSec/SquidC5

Made for: GitHub Copilot.

Per session 120 This file is loaded in full into every session.
When invoked 120 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.00120 $0.00120
Opus 5 $0.00060 $0.00060
Sonnet 5 $0.00024 $0.00024
Haiku 4.5 $0.00012 $0.00012

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

Security

Grade A, and why

SquidC5 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 · 11 lines

What it actually says

GitHub Copilot instructions for SquidC5

Read and obey root AGENTS.md.

  • Security-first C2 for authorized testing only
  • Do not weaken MCP tool allow-lists or Admin AI sanitize_untrusted boundaries
  • Do not commit tokens, API keys, or data/ contents
  • Prefer deterministic templates over autonomous agent loops
  • Operator CLI is sc5 - keep help/README/AGENTS in sync when adding commands
  • Docker compose uses host networking for listener ports; document privileged-port sysctl for <1024
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 · 11 lines · 120 tokens per session scan A a691dcb374ee

Subscribe to this mod's changes

SquidC5 copilot-instructions.md is an instructions file published in the GitHub repository SquidSec/SquidC5 (51 stars, last pushed 12d ago), licensed MIT. It adds 120 tokens to every session, about $0.0006 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.