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 skills add elevanaltd/HestAI-MCP --skill documentation-placementgit clone --depth 1 https://github.com/elevanaltd/HestAI-MCPWrote 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/elevanaltd/hestai-mcp/documentation-placement)<a href="https://agentmods.dev/skills/elevanaltd/hestai-mcp/documentation-placement"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/documentation-placement.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.1 | $0.00055 | $0.02670 |
| Opus 5 | $0.00028 | $0.01335 |
| Sonnet 5 | $0.00011 | $0.00534 |
| Haiku 4.5 | $0.00006 | $0.00267 |
Grade A, and why
documentation-placement 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 7d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
===DOCUMENTATION_PLACEMENT=== META: TYPE::SKILL VERSION::"2.3" STATUS::ACTIVE COMPRESSION_TIER::AGGRESSIVE DOMAIN::HERMES[communication]+HESTIA[structure]
§1::CORE_PRINCIPLE
TIMELINE_TEST::[ IF[document_before_code]→.hestai/north-star/|.hestai/rules/, IF[document_describes_implementation]→docs/, IF[document_guides_implementation]→docs/, IF[operational_state_or_tracking]→.hestai/state/context/, IF[session_or_handoff]→.hestai/state/sessions/ ]
RATIONALE::"Timeline→placement: planning=.hestai/, implementation=docs/, operational=.hestai/state/"
CANONICAL_REFERENCE::.hestai-sys/standards/rules/visibility-rules.oct.md
§2::REPOSITORY_STRUCTURE
// Per visibility-rules.oct.md v1.7
SYSTEM_GOVERNANCE[.hestai-sys/]::[ READ_ONLY[injected_from_src/hestai_mcp/_bundled_hub/], standards/workflow/→"System North Star (000-SYSTEM-HESTAI-NORTH-STAR.md)", standards/rules/→"Naming standard, visibility rules, test standards", agents/→"Agent definition templates (.oct.md)", templates/→"Project scaffolding templates", library/skills/→"Ecosystem-wide operational skills", library/agents/→"Agent definitions", library/patterns/→"Reusable patterns and examples", library/schemas/→"Schema definitions", library/octave/→"OCTAVE usage guides", tools/→"System utility scripts (validators, checkers)" ]
NOTE::"Agents CANNOT place artifacts in .hestai-sys/ — it is injected read-only at runtime"
PROJECT_GOVERNANCE[.hestai/]::[ north-star/→"North Star documents (000-*-NORTH-STAR.md + components/)", decisions/→"Compiled governance decisions (debate outcomes, NOT ADRs)", rules/→"Project standards, methodology, workflow guidance, specs", schemas/→"Schema definitions" ]
DEVELOPER_DOCS[docs/]::[ adr/→"ADR-NNNN-topic.md (GitHub issue-based numbering per ADR-0031)", api/→"API endpoint documentation", development/→"Setup guides", deployment/→"Deployment guides" ]
OPERATIONAL_STATE[.hestai/state/]::[ context/→"PROJECT-CONTEXT.md, PROJECT-CHECKLIST.md, PROJECT-HISTORY.md", context/apps//→"APP-CONTEXT.md, APP-CHECKLIST.md, APP-HISTORY.md", sessions/active/→"Active session working state", sessions/archive/→"YYYY-MM-DD---octave.oct.md (committed) + raw.jsonl (gitignored)", reports/→"YYYY-MM-DD-* audit reports, scan outputs, quality gate evidence" ]
DEBATE_ARTIFACTS[debates/]::[ json→GITIGNORED[full_debate_machine_format], oct.md→COMMITTED[compressed_debate_synthesis] ]
CLAUDE_CODE[.claude/]::[ agents/→"Agent definitions (.oct.md)", commands/→"Slash commands", skills/→"Project-specific skills (per-repo, NOT ecosystem-wide)", hooks/→"Git workflow automation" ]
NOTE::.claude/skills/→project_specific|.hestai-sys/library/skills/→ecosystem_wide
§3::PHASE_ARTIFACT_MAPPING
// Lifecycle: Spec (the plan) → Report (the evidence) → Doc (the product) // Artifacts graduate through the lifecycle as phases progress
PLACEMENT::[ D1_NORTH_STAR::.hestai/north-star/[immutable_anchor], D2_IDEAS_CONSTRAINTS_DESIGN::.hestai/rules/specs/[active_spec], D3_BLUEPRINT::.hestai/rules/specs/[spec_MIGRATES_to_docs/_at_B1_gate], B0_VALIDATION::.hestai/state/reports/[gate_evidence], B1_BUILD_PLAN::.hestai/rules/specs/[task_breakdown_for_B2], B2_IMPLEMENTATION_LOG::.hestai/state/reports/[evidence_stream], B3_QA_SECURITY::.hestai/state/reports/[audit_trail], B4_HANDOFF_USER_GUIDE::docs/[graduated_permanent_documentation] ]
GRADUATION_RULES::[ D3_blueprint→migrates_from_.hestai/rules/specs/_to_docs/_at_B1_gate, B0_architectural_decisions→recorded_as_ADRs_in_docs/adr/, B4_handoff_docs→graduate_from_draft_to_docs/_at_delivery ]
ADR_SUPREMACY::[ RULE::"When in doubt between .hestai/decisions/ and docs/adr/ → choose docs/adr/", .hestai/decisions/→compiled_debate_decisions[agent_facing_OCTAVE_governance_outcomes], docs/adr/→all_architecture_implementation_design_decisions[developer_facing_markdown], DISTINCTION::"debate-hall exports→.hestai/decisions/[.oct.md] | developer decisions→docs/adr/[.md]" ]
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.
- 7d ago First seen · 275 lines · 55 tokens per session scan A 76e8a6f2e8ab
documentation-placement is a skill published in the GitHub repository elevanaltd/HestAI-MCP (0 stars, last pushed today), licensed Apache-2.0. It adds 55 tokens to every session and 2,670 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…