Borrowing it
Nothing to install: this file belongs to PackmindHub/packmind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PackmindHub/packmind/main/.claude/skills/agentic-doc-ingest/SKILL.mdgit clone --depth 1 https://github.com/PackmindHub/packmindWrote 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/packmindhub/packmind/agentic-doc-ingest)<a href="https://agentmods.dev/skills/packmindhub/packmind/agentic-doc-ingest"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/agentic-doc-ingest/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/packmindhub/packmind/agentic-doc-ingest"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/agentic-doc-ingest.svg" alt="Reviewed on agentmods" width="80" 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.00093 | $0.00670 |
| Opus 5.5 | $0.00037 | $0.00268 |
| Sonnet 5.5 | $0.00019 | $0.00134 |
| Haiku 4.5 | $0.00009 | $0.00067 |
Grade A, and why
agentic-doc-ingest 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 1mo 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation ingest
You write documentation from three files and no code:
.claude/features/<slug>/charter.md what was meant to be built, and for whom
.claude/features/<slug>/decisions.md what was decided, and what was rejected
.claude/features/<slug>/records.jsonl what each unit actually did
Why you do not read the code
Because you do not have to, and that is deliberate. The records carry
public_surface_changed and behaviour_delta on every unit — the executor
filled them in while it still had the change in front of it, which is the
cheapest and most accurate moment that information exists.
Read a source file only to check a specific name or signature you are about to print. Not to survey, not to "understand the feature".
Why the decision log alone is not enough
The decision log records intent. Documentation built from it describes what was meant, not what was built.
The deviations field across the records is exactly that gap. Read it early —
where a unit deviated, the log is wrong and the record is right, and a document
that follows the log will confidently describe something that does not exist.
The two documents are not the same document
Decide which you were asked for; do not blend them.
User-facing. Driven by acceptance criteria marked user-visible: yes and
decisions marked user-visible: yes. Task-oriented, no implementation detail.
For Packmind this lands in apps/doc/ — hand off to the
creating-end-user-documentation-for-packmind skill for house style and
placement rather than inventing your own.
Technical. Driven by public_surface_changed across the records, plus the
decisions and their rejected alternatives. Rationale is already written in the
decision log — link to it, do not paraphrase it into prose that will drift.
The coverage check
Before you finish, verify: every entry marked user-visible: yes, in both the
charter and the decision log, has a corresponding mention in what you wrote.
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.
- 1mo ago First seen · 66 lines · 93 tokens per session scan A ea469442ef44
agentic-doc-ingest is a skill published in the GitHub repository PackmindHub/packmind (319 stars, last pushed 4d ago), licensed Apache-2.0. It adds 93 tokens to every session and 670 once invoked, about $0.0004 per session on Opus 5.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-09-17.
Other skills, from other repositories
ce-compound
Document a recently solved problem or durable project vocabulary in docs/solutions/ or CONCEPTS.md. Use when capturing a learning after work.
ce-work
Execute a plan or concrete work prompt end-to-end. Use when implementing from docs/plans, a spec path, or a clear build request; use ce-debug for open-ended bugs.
sdd
Execute the Liatrio Spec-Driven Development (SDD) workflow when explicitly invoked by the user. NOTE: this skill is NOT intended to be dynamically loaded or automatically triggered; it should only ever be explicitly called by the user.
loadout-import-workflow
Import another repo's command/skill suite into loadout as a workflow. Use when the user points at an agent framework, plugin, or command pack (e.g. a GitHub repo, a .claude/commands/ directory, a skills pack) and wants its process turned into a loadout [[workflows]] entry — "import this workflow", "turn this plugin…
ce-commit-push-pr
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
loadout-migrate
Migrate existing global AI agent instructions into loadout. Use when adopting loadout, importing a CLAUDE.md / AGENTS.md / global agent rules into loadout, setting up /.config/loadout/config.toml, or turning prose agent instructions into reusable fragments and stack-targeted profiles.