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/modiqo/skillspec/pdf-processingnpx skills add modiqo/skillspec --skill pdf-processinggit clone --depth 1 https://github.com/modiqo/skillspecWhat 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.00049 | $0.02700 |
| Opus 5 | $0.00024 | $0.01350 |
| Sonnet 5 | $0.00010 | $0.00540 |
| Haiku 4.5 | $0.00005 | $0.00270 |
Grade A, and why
pdf-processing 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 2d 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.
This is a copy
83% identical to generic-skill-creator — 23 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PDF Processing SkillSpec
Structured representation of a multi-file PDF skill with references, code snippets, artifacts, and an ordered form-filling recipe.
This skill is a thin loader for the colocated skill.spec.yml. The spec is the source of truth for routes, rules, dependencies, imports, resources, recipes, tests, and trace requirements. Do not treat the spec as background prose; treat it as the execution contract for this task.
Runtime Contract
-
Load
./skill.spec.ymlfrom this skill folder before taking task actions. -
When the
skillspecCLI is available and the spec shape is unfamiliar, runskillspec sensemake ./skill.spec.yml --view indexto learn the section roles, counts, query handles, and navigation grammar without dumping the full YAML. -
Then create the ordered phase plan and current-route action checklist:
skillspec plan ./skill.spec.yml --input='<user task>' --trace-dir "${PWD}/.skillspec/traces" skillspec act ./skill.spec.yml --input='<user task>' --run <run_dir> --phase <phase-id> -
Strip skill invocation prefixes such as
/my-skill,$my-skill, or/durable-executor-specbefore passing--input. -
Preserve the emitted trace
run_dir. -
Read the full phase plan and action checklist before using tools. Treat them as the active execution SOP, not as advice. The
PHASE TOOL BOUNDARY - HARDsection is the permission boundary for the next action. -
For each execution phase, run
skillspec act ./skill.spec.yml --input='<user task>' --run <run_dir> --phase <phase-id>before acting, record phase progress in<run_dir>/execution.jsonl, then runskillspec progress show ./skill.spec.yml --run <run_dir>to see completed, current, blocked, and remaining phases. -
Pull active details with
skillspec query ./skill.spec.yml <handle> --view summaryand relationship edges withskillspec refs ./skill.spec.yml <handle> --view summary. Prefer precise handles such asrule:<id>,rule:<id>.forbid,command:<id>.requires, andstate:<id>.nextover reading the whole spec. -
Before every substrate/tool call, apply the phase tool boundary and checklist allow/deny questions. Any unlisted tool, data source, execution substrate, provider, adapter, CLI, browser mode, API, or skill requires explicit user permission before use. The selected route and matched rules override lower-level skill defaults and generic tool preferences.
-
When the CLI is available after a trace exists, run
skillspec trace align ./skill.spec.yml --decision-trace <run_dir>and, when structured action evidence exists, add--execution-trace <run_dir>/execution.jsonl. The command writes<run_dir>/alignment.json; report the alignment status, meaning, model layers, evidence gaps, user-facing proof rows, summary, and trace path. -
If
skillspec plan,skillspec act, orskillspec progressis unavailable, fall back toskillspec decide, then manually construct the same ordered phase checklist and progress notes before using tools. If the CLI is unavailable, readskill.spec.ymldirectly and apply the same contract manually. Do not expand this loader into a second source of truth.
What ships with it
3 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.
- 2d ago First seen · 119 lines · 49 tokens per session scan A d3638fbf2b68
pdf-processing is a skill published in the GitHub repository modiqo/skillspec (737 stars, last pushed 24d ago), licensed Apache-2.0. It adds 49 tokens to every session and 2,700 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to generic-skill-creator, differing in 23 lines, and is treated as a copy.
Other skills, from other repositories
writing-e2e-flows
Use when a feature or fix in future-agi needs an end-to-end Playwright flow under e2e/ — a new flow for user-visible behaviour, an update to a flow whose pinned endpoint, route, table or selector changed, or when a review flagged missing E2E coverage. Also use to check whether an existing flow already pins an…
reviewing-prs
Use when asked to review a pull request, branch, or diff — before approving, as a self-review before opening a PR, to judge whether a PR is ready — 'is PR 123 mergeable?', 'anything blocking here?' — or to answer 'does this change need an E2E flow'. Applies the FutureAGI coding standards and, in repos with an e2e/…
ashfox
Create, edit, review, animate, and export game-ready low-poly assets in the ashfox web workbench through an AI agent. Use for low-poly modeling, deterministic textures and UVs, rigs, idle or motion animation, GLB, Bedrock, or GeckoLib exports, and Blockbench-free asset production.
ui-2026-cinematic
Cinematic 3D / scroll-driven / motion design skill for landing pages in 2026. Use when building marketing pages, SaaS sites, or product showcases that need scroll storytelling, 3D elements, micro-interactions, kinetic typography, or glassmorphism. Encodes modern best practices from Figma, Anthropic, Apple, Vercel.…
template-skill
A minimal template for creating a new FDE Consultant Skill (Apache-2.0). Use as starting point for any new skill.
production-autopsy
Start here. Audits a deployed ML or LLM or agent system that scores well on evaluation but fails, regresses, or behaves unexpectedly in production. Runs a reproducible root-cause "autopsy": frames the eval-to-deployment gap, reproduces the production failure, quantifies it by slice, tests confidence calibration under…