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/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.01184 | $0.01184 |
| Opus 5 | $0.00592 | $0.00592 |
| Sonnet 5 | $0.00237 | $0.00237 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
linkedin.asisaga.com 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Instructions
Core Principles
1. Update, Don't Replace
NEVER create new summary/completion docs for every change.
- Update existing documentation with new sections
- Add version headers for significant changes
- Use "Last Updated" dates to track currency
- Append to existing guides rather than creating new ones
2. Consolidate Similar Content
- Merge scattered guides into comprehensive ones
- Cross-reference related documentation
- Eliminate redundant files
- Maintain single source of truth
3. Progressive Enhancement
- Add new sections to existing guides
- Update code examples inline
- Expand existing sections rather than duplicate
- Keep historical context when relevant
4. Proper Archival
Completed implementation work:
- Move to
/docs/archive/implementations/ - Don't delete - preserve for historical reference
- Link from main docs if still relevant
- Keep active docs current and actionable
Documentation Structure
Active Documentation (/docs/)
Root Level - Essential, living documentation:
README.md- Documentation index and navigation- Domain-specific guides (ontology, layout, semantic, etc.)
- Quick starts and references
- Current implementation guides
/docs/guides/ - User-facing tutorials:
- Quick start guides, technical how-tos, best practices, tool documentation
/docs/specifications/ - Technical specifications:
- System architecture, component specs, design tokens, API references
Historical Documentation (/docs/archive/)
/docs/archive/implementations/ - Completed work:
- Implementation summaries, version-specific enhancements, feature completion records
/docs/archive/audits/ - Code audits:
- Quality assessments, fix summaries, before/after comparisons
/docs/archive/refactorings/ - Major refactors:
- Refactoring summaries, breaking changes, migration paths
When to Create New Documentation
Create New When:
- New Feature/System - Documenting something that doesn't exist yet
- New User Guide - Tutorial for a distinct use case
- New Specification - Formal spec for a new subsystem
- Major Version - Breaking changes require new migration guide
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 · 157 lines · 1,184 tokens per session scan A 78798026e743
linkedin.asisaga.com 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 1,184 tokens to every session, about $0.0059 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.