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 agentmods add instructions/asisaga/linkedin.asisaga.com/github-instructionsgit clone --depth 1 https://github.com/ASISaga/linkedin.asisaga.comWhat 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.00454 | $0.00454 |
| Opus 5 | $0.00227 | $0.00227 |
| Sonnet 5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00045 | $0.00045 |
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.
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
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.
- yesterday First seen · 82 lines · 454 tokens per session scan A 8ca0a75e0463
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.
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.
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).
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.
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).
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.
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.