linkedin.asisaga.com github-instructions.instructions.md

A set of rules for instruction files in .github/instructions/, a folder where GitHub Copilot can load guidance for matching files.

In plain words
What is it for?
Use it when writing or reviewing YAML headers, file-matching patterns, coding rules, and validation commands for instruction files.
Why use it?
It helps keep file-specific guidance consistent, focused, and automatically applied to the right files.

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/asisaga/linkedin.asisaga.com/github-instructions
Clone the repo
git clone --depth 1 https://github.com/ASISaga/linkedin.asisaga.com

Made for: GitHub Copilot.

Per session 454 This file is loaded in full into every session.
When invoked 454 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.00454 $0.00454
Opus 5 $0.00227 $0.00227
Sonnet 5 $0.00091 $0.00091
Haiku 4.5 $0.00045 $0.00045

Measured yesterday against content hash 8ca0a75e0463, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

linkedin.asisaga.com github-instructions.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 yesterday.

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/instructions/github-instructions.instructions.md · 82 lines

What it actually says

Instruction Files Standards

Purpose

Instruction files in .github/instructions/ are path-activated coding standards that auto-load when editing files matching their applyTo glob patterns.

File Format

YAML Frontmatter (required):

---
applyTo: "glob/pattern/**"
description: "Brief description for agent discovery"
---

Requirements

  • applyTo: Specific glob pattern targeting exact file types
  • description: One-line purpose (helps agents discover context)
  • Body: Minimal coding standards, reference specs/docs for details

Content Guidelines

DO Include:

  • File format requirements
  • Coding standards specific to the file type
  • Tool integration commands (npm scripts, validation scripts)
  • References to specs/docs for detailed patterns

DON'T Include:

  • Detailed specifications (belong in .github/specs/)
  • Implementation guides (belong in .github/docs/)
  • Duplicate content from copilot-instructions.md
  • Overly broad applyTo patterns

Example Structure

---
applyTo: "**/*.example"
description: "Standards for example files"
---

# Example Files Instructions

## File Format
[Format requirements]

## Tool Integration
```bash
npm run validate

References

Specification: .github/specs/example-spec.md


## Validation

Before committing:
1. YAML frontmatter is valid
2. applyTo pattern is specific and focused
3. Content references specs/docs, doesn't duplicate
4. No overlap with other instruction files

## Related Documentation

→ **Instructions spec**: `.github/specs/instructions.md` - Detailed instruction file specification
→ **Framework**: `.github/docs/agent-intelligence-framework.md` - Complete system specification
→ **Path-specific instructions**: `.github/docs/path-specific-instructions.md` - How glob patterns work

---

**Version**: 1.1 - Added spec references for dogfooding  
**Last Updated**: 2026-02-14
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. yesterday First seen · 82 lines · 454 tokens per session scan A 8ca0a75e0463

Subscribe to this mod's changes

linkedin.asisaga.com github-instructions.instructions.md is an instructions file published in the GitHub repository ASISaga/linkedin.asisaga.com (0 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 454 tokens to every session, about $0.0023 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.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

buildNext

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

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit 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,040 tokens

langchain AGENTS.md

Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens