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-docsgit 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.00593 | $0.00593 |
| Opus 5 | $0.00296 | $0.00296 |
| Sonnet 5 | $0.00119 | $0.00119 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
linkedin.asisaga.com github-docs.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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Files Standards
Purpose
Documentation files in .github/docs/ are implementation guides and references that help users understand and use the agent intelligence system.
File Naming
- Use kebab-case:
guide-name.md - Be descriptive:
agent-system-overview.mdnotoverview.md - Include type:
getting-started-guide.md,api-reference.md
Content Structure
# Documentation Title
**Last Updated**: YYYY-MM-DD
**Audience**: [Developers | Contributors | Users]
## Introduction
[What this document covers]
## Prerequisites
[What you need to know before reading]
## Content
[Main documentation content]
## Examples
[Practical examples]
## Next Steps
[What to read/do next]
## References
[Related docs and specs]
Content Guidelines
✅ DO Include:
- Step-by-step guides
- Tutorials and walkthroughs
- Usage examples
- Troubleshooting tips
- Quick reference materials
❌ DON'T Include:
- Detailed specifications (belong in
.github/specs/) - Path-specific coding standards (belong in
.github/instructions/) - Duplicate content from other docs
Documentation Types
Guides: How to accomplish specific tasks
getting-started-guide.mdmigration-guide.md
References: Quick lookup information
agent-quick-reference.mdapi-reference.md
Overviews: System understanding
agent-system-overview.mdarchitecture-overview.md
Cross-References
Docs should be:
- Referenced from: copilot-instructions.md, instruction files, specs
- Reference: Specs for technical details
- Link to: Other related docs
Validation
Before committing:
- Follows naming convention
- Has clear audience and prerequisites
- Examples are tested and work
- Links to other docs/specs are correct
- No duplication with specs or instructions
Related Documentation
→ Agent framework: .github/specs/agent-intelligence-framework.md - Complete system specification
→ Architecture: /docs/specifications/architecture.md - System architecture and organization
→ Agent guidelines: /docs/specifications/github-copilot-agent-guidelines.md - Standards and best practices
→ Self-learning: /docs/specifications/agent-self-learning-system.md - Dogfooding and Ouroboros
→ Agent philosophy: .github/docs/agent-philosophy.md - Core principles
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 · 101 lines · 593 tokens per session scan A d77636448b32
linkedin.asisaga.com github-docs.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 593 tokens to every session, about $0.0030 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
n8n-skills CLAUDE.md
Instructions for czlonkowski/n8n-skills, covering claude.md, project overview, repository structure, the 14 skills and 1. n8n expression syntax.
Tutorial_AwesomeModernCPP AGENTS.md
Instructions for Awesome-Embedded-Learning-Studio/Tutorial_AwesomeModernCPP, covering agents.md, 这是什么, 通用 essentials(所有 agent 必读) and 你来做什么?(按场景路由).
python-cheatsheet copilot-instructions.md
Copilot instructions for labex-labs/python-cheatsheet, covering python cheatsheet - ai coding assistant instructions, project overview, architecture & key patterns, content structure and routing & layout system.
fix-quera AGENTS.md
Instructions for AlirezaKeshavarz83/fix-quera, covering agent guidance, project shape, visual style, quera page data findings and compatibility findings.
ab900 CLAUDE.md
Instructions for timothywarner-org/ab900, covering claude.md, repository purpose, architecture, commands and 2. non-ascii punctuation -- must return zero.
agentconfig.org AGENTS.md
Instructions for agentconfig/agentconfig.org, covering agent instructions for agentconfig.org, project overview, target audience, site structure and tech stack.