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.
npx skills add G1Joshi/Agent-Skills --skill github-copilotgit clone --depth 1 https://github.com/G1Joshi/Agent-SkillsWrote 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.
[](https://agentmods.dev/skills/g1joshi/agent-skills/github-copilot)<a href="https://agentmods.dev/skills/g1joshi/agent-skills/github-copilot"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/github-copilot/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/g1joshi/agent-skills/github-copilot"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/github-copilot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00038 | $0.01222 |
| Opus 5.5 | $0.00015 | $0.00489 |
| Sonnet 5.5 | $0.00008 | $0.00244 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade C, and why
github-copilot scanned grade C with 1 finding 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 17d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- .github/copilot-instructions.md --> How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot
GitHub Copilot is an enterprise AI pair programming assistant, providing inline completions, multi-file code editing via Copilot Edits, pull request reviews, and CLI integration.
When to Use
- In-Editor AI Pair Programming: Generating functions, documentation, and boilerplate across VS Code, JetBrains, and Neovim.
- Repository-Level Architectural Context: Using Copilot Chat with workspace awareness (
@workspace). - Standardizing Team Prompting: Authoring
.github/copilot-instructions.mdto enforce organizational coding standards. - Automated Pull Request Summarization: Generating detailed PR summaries and test plans within GitHub Enterprise.
Quick Start
Configure custom repository instructions in .github/copilot-instructions.md:
# GitHub Copilot Instructions
- Use modern ES2022+ syntax and TypeScript 5.
- Always validate incoming API payloads using Zod schemas.
- Do not add comments describing self-explanatory lines.
- Write unit tests using Vitest with AAA (Arrange-Act-Assert) pattern.
Core Concepts
Project-Wide Custom Instructions (.github/copilot-instructions.md)
Configuring persistent AI developer guidelines:
# .github/copilot-instructions.md
Repository Standards
- Language: TypeScript 5.5+ with strict mode enabled.
- Framework: Next.js 15 (App Router), Tailwind CSS v4.
- Database: Drizzle ORM with PostgreSQL.
- Testing: Vitest for unit tests, Playwright for e2e.
Coding Conventions
1. Always declare explicit return types on public functions.
2. Prefer async/await over raw Promises.
3. Use early returns and guard clauses to minimize nested blocks.
4. Never suggest 'any'; use typed generics or unknown.
5. All new business functions must include an accompanying unit test file.
Slash Commands & Context Modifiers in Copilot Chat
Directing the AI assistant with precision:
# Prompt in Copilot Chat
@workspace /explain How is user authentication state persisted across server and client components?
# Generating Unit Tests
/tests Generate comprehensive unit tests covering edge cases for validateOrderPayload()
# Fixing Errors
@terminal /fix Resolve this TypeScript compilation error with discriminated unions
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.
- 17d ago Changed · +7 lines 194ae62520b0
- 21d ago Changed · +91 lines · +18 tokens per session scan A → C 82060895a026
- 1mo ago First seen · 45 lines · 20 tokens per session scan A 749c730e97e3
github-copilot is a skill published in the GitHub repository G1Joshi/Agent-Skills (15 stars, last pushed 18d ago), licensed MIT. It adds 38 tokens to every session and 1,222 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
observability-and-instrumentation
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
spec-driven-development
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans…
using-agent-skills
Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand. This is the meta-skill that governs how all other skills are discovered and invoked.