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 skills/asisaga/linkedin.asisaga.com/documentation-manager-agentnpx skills add ASISaga/linkedin.asisaga.com --skill documentation-manager-agentgit 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/skills/asisaga/linkedin.asisaga.com/documentation-manager-agent)<a href="https://agentmods.dev/skills/asisaga/linkedin.asisaga.com/documentation-manager-agent"><img src="https://agentmods.dev/badge/skills/asisaga/linkedin.asisaga.com/documentation-manager-agent.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.00054 | $0.01010 |
| Opus 5 | $0.00027 | $0.00505 |
| Sonnet 5 | $0.00011 | $0.00202 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
documentation-manager-agent 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Manager Agent
Role: Documentation Quality and Organization Specialist
Scope: All documentation in /docs, repository root, agent docs
Version: 1.1 - High-Density Refactor
Purpose
Ensure documentation follows organizational standards, remains maintainable, and avoids redundancy. Enforces principles from .github/instructions/docs.instructions.md through automated validation.
When to Use This Skill
Activate when:
- Creating/updating documentation files
- Reorganizing documentation structure
- Moving completed work to archive
- Auditing documentation quality
- Checking for redundant content
- Validating cross-references/links
Core Principles
Update, Don't Replace:
- ✅ Update existing files with new sections
- ✅ Add version headers for changes
- ❌ Don't create
FEATURE-v2.3.0.mdfor every change
Single Source of Truth:
- ✅ Merge scattered guides
- ✅ Eliminate duplicates
- ❌ Don't duplicate content across files
Proper Archival:
- ✅ Move completed work to
/docs/archive/implementations/ - ✅ Preserve historical reference
- ❌ Don't leave completed docs in active area
→ Complete standards: .github/instructions/docs.instructions.md
Validation Scripts
1. Structure Validation
./.github/skills/documentation-manager-agent/scripts/validate-doc-structure.sh
# Checks:
# - Required files (README.md, INDEX.md)
# - Required directories
# - Misplaced files
# - Version-numbered files
2. Link Validation
./.github/skills/documentation-manager-agent/scripts/validate-doc-links.sh docs/
# Checks:
# - Broken internal links
# - Missing referenced files
# - Invalid anchor links
3. Redundancy Detection
./.github/skills/documentation-manager-agent/scripts/detect-doc-redundancy.sh
# Finds:
# - Similar filenames
# - Redundant naming patterns
# - Content similarity
# - Old/new file pairs
4. Metadata Validation
./.github/skills/documentation-manager-agent/scripts/check-doc-metadata.sh docs/specifications/
# Checks:
# - Version headers
# - "Last Updated" dates
# - Outdated timestamps
# - Versioning consistency
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 155 lines · 54 tokens per session scan A 669477216212
documentation-manager-agent is a skill published in the GitHub repository ASISaga/linkedin.asisaga.com (0 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 1,010 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…