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/promptsgit clone --depth 1 https://github.com/ASISaga/linkedin.asisaga.comWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/asisaga/linkedin.asisaga.com/prompts)<a href="https://agentmods.dev/instructions/asisaga/linkedin.asisaga.com/prompts"><img src="https://agentmods.dev/badge/instructions/asisaga/linkedin.asisaga.com/prompts.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00348 | $0.00348 |
| Opus 5 | $0.00174 | $0.00174 |
| Sonnet 5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade B, and why
linkedin.asisaga.com prompts.instructions.md scanned grade B with 1 finding 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 3d ago.
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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: ['*'] What it actually says
Prompt Files Instructions
File Format
YAML Frontmatter (required):
---
description: "Brief agent purpose (1-256 chars)"
name: "agent_name" # snake_case
agent: "agent"
model: "claude-3-5-sonnet-20241022"
tools: ['*']
---
Body Structure
- Agent role and purpose
- Core responsibilities (actionable list)
- When to use (activation triggers)
- Workflows and examples
- Tool integration
- Related documentation
Tool Integration
Reference existing tools, never duplicate:
npm test # Run all tests
npm run test:scss # SCSS compilation
npm run lint:scss # Stylelint validation
Validation scripts:
./.github/skills/[skill-name]/scripts/validate-*.sh
Keep Focused
Reference detailed patterns instead of duplicating:
→ Specifications: .github/specs/prompts.md
→ Documentation: .github/docs/
Related Documentation
→ Prompt spec: .github/specs/prompts.md - Detailed prompt file specification
→ Framework: .github/docs/agent-intelligence-framework.md - Complete system framework
→ Agent philosophy: .github/docs/agent-philosophy.md - Core principles
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.
- 3d ago First seen · 61 lines · 348 tokens per session scan B e1ae29d1a36a
linkedin.asisaga.com prompts.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 348 tokens to every session, about $0.0017 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
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).
spec-kit AGENTS.md
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.
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.
langchain AGENTS.md
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.
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).
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.