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-specsgit 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.00764 | $0.00764 |
| Opus 5 | $0.00382 | $0.00382 |
| Sonnet 5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
linkedin.asisaga.com github-specs.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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specification Files Standards
Purpose
Specification files in .github/specs/ contain detailed patterns and frameworks that instruction files reference. They define the "what" and "how" of systems.
Specifications are created and updated using the Spec Manager Agent and its three SDD workflows.
→ SDD workflow: .github/specs/spec-driven-development.md
→ Spec manager agent: .github/agents/spec-manager.agent.md
Spec-Driven Development (SDD) Workflow
New feature specifications are created through the Copilot agent intelligence system:
| Stage | Prompt | Output |
|---|---|---|
| 1. Specify | spec-create.prompt.md |
specs/NNN-slug/spec.md |
| 2. Plan | spec-plan.prompt.md |
plan.md, research.md, data-model.md, contracts/, quickstart.md |
| 3. Tasks | spec-tasks.prompt.md |
specs/NNN-slug/tasks.md |
All specs created by the agent are placed in specs/<NNN>-<slug>/. Specs in .github/specs/ document the agent intelligence system itself and follow the standard format below.
File Naming
- Use kebab-case:
system-name.md - Be descriptive:
ontological-design-system.mdnotontology.md - Include version if needed:
agent-framework-v2.md
Content Structure
# Specification Title
**Version**: X.Y.Z
**Status**: Draft | Active | Deprecated
**Last Updated**: YYYY-MM-DD
## Overview
[Brief description of what this specifies]
## Scope
[What's included and excluded]
## Specification
[Detailed patterns, frameworks, requirements]
## Examples
[Code examples and use cases]
## Validation
[How to verify compliance]
## References
[Related specs and docs]
Content Guidelines
✅ DO Include:
- Detailed technical specifications
- Complete frameworks and patterns
- Code examples and templates
- Architecture diagrams
- Validation criteria
❌ DON'T Include:
- Step-by-step tutorials (belong in
.github/docs/) - Path-specific coding standards (belong in
.github/instructions/) - Project-specific implementations (reference from specs)
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 · 105 lines · 764 tokens per session scan A 09ce777007a3
linkedin.asisaga.com github-specs.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 764 tokens to every session, about $0.0038 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.