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/skillsgit 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/skills)<a href="https://agentmods.dev/instructions/asisaga/linkedin.asisaga.com/skills"><img src="https://agentmods.dev/badge/instructions/asisaga/linkedin.asisaga.com/skills.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.00448 | $0.00448 |
| Opus 5 | $0.00224 | $0.00224 |
| Sonnet 5 | $0.00090 | $0.00090 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
linkedin.asisaga.com skills.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 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.
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
Skill Files Instructions
File Format
YAML Frontmatter (required):
---
name: skill-name # kebab-case, matches directory
description: One-sentence purpose with keywords (1-1024 chars)
license: MIT
metadata:
author: ASISaga
version: "2.1"
category: design-system
role: specialist-role
allowed-tools: Bash(npm:*) Read Edit
---
Body Structure
- Role and scope statement
- Purpose paragraph
- "When to Use This Skill" triggers
- Core Principles or Responsibilities
- Workflows and Examples
- Tool Integration
- Validation Instructions
- Related Documentation
Directory Structure
.github/skills/skill-name/
├── SKILL.md # This file
├── scripts/ # Validation scripts
├── references/ # Detailed specs
└── assets/ # Visual examples (optional)
Tool Integration
Reference npm scripts:
npm test
npm run test:scss
npm run lint:scss
Validation scripts pattern:
./.github/skills/[skill-name]/scripts/validate-*.sh
Keep Concise
Detailed specifications belong in references/ subdirectory, not in SKILL.md.
→ Specifications: .github/specs/skills.md
→ Documentation: .github/docs/
→ agentskills.io spec: https://agentskills.io
Related Documentation
→ Skill spec: .github/specs/skills.md - Detailed skill file specification
→ Framework: .github/docs/agent-intelligence-framework.md - Framework specification
→ Agent philosophy: .github/docs/agent-philosophy.md - Design 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 · 78 lines · 448 tokens per session scan A d5f771e535b9
linkedin.asisaga.com skills.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 448 tokens to every session, about $0.0022 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
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.