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/smith-network-solutions/threadknot/pptxnpx skills add smith-network-solutions/threadknot --skill pptxgit clone --depth 1 https://github.com/smith-network-solutions/threadknotWhat 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.00081 | $0.01380 |
| Opus 5 | $0.00041 | $0.00690 |
| Sonnet 5 | $0.00016 | $0.00276 |
| Haiku 4.5 | $0.00008 | $0.00138 |
Grade A, and why
pptx 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.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PowerPoint decks (.pptx)
python-pptx for everything. The library is capable, but the deck you get is only as good as your handling of two things: layouts and units.
Layouts first — always
A slide is created from a layout, and the layout supplies the placeholders you then fill. Guessing layout indices produces the classic broken deck: text in the wrong place, a title that is really a body box, branding that silently disappears.
scripts/inspect_pptx.py template.pptx --layouts
Prints every layout in the template with its index, name, and each placeholder's index, type and position. Run this before authoring against any template, including the default one — index 1 is "Title and Content" in the stock template but frequently something else in a corporate deck.
from pptx import Presentation
prs = Presentation("template.pptx") # or Presentation() for the stock template
layout = prs.slide_layouts[1] # verify this index with --layouts first
slide = prs.slides.add_slide(layout)
slide.shapes.title.text = "Q1 results"
body = slide.placeholders[1] # placeholder IDX, not position in a list
body.text = "Revenue up 14%"
for line in ["Costs flat", "Margin improved"]:
para = body.text_frame.add_paragraph()
para.text = line
para.level = 1 # indent level, 0-4
Building on the user's template is what preserves their fonts, colours and
master — always prefer it to Presentation() plus manual styling.
Writing your own script
The scripts here declare their dependencies inline (PEP 723) and run under
uv, so they work with nothing installed. Do the same for scripts you write
rather than pip-installing or building a venv — on a modern distro the system
Python is PEP-668 managed and pip install fails outright:
#!/usr/bin/env -S uv run --quiet --script
# /// script
# requires-python = ">=3.10"
# dependencies = ["python-pptx>=1.0"]
# ///
Then chmod +x build.py && ./build.py, or just
uv run --with 'python-pptx>=1.0' python build.py (quote the spec — > and [ are shell
metacharacters).
If uv is genuinely unavailable, fall back to a venv — but check for uv first.
What ships with it
5 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 · 140 lines · 81 tokens per session scan A ba81f5cc3e6d
pptx is a skill published in the GitHub repository smith-network-solutions/threadknot (5 stars, last pushed 8d ago), licensed Apache-2.0. It adds 81 tokens to every session and 1,380 once invoked, about $0.0004 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
reconciliation
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
rove
Use when controlling Rove tasks, parallel coding attempts, hosted agent sessions, task lifecycle, or the daemon-owned issue tracker from a shell. Also the ONLY channel for messaging another agent session on this machine — rove api send, never a peer/MCP side channel.
general-video
The fallback workflow for authoring custom HyperFrames video compositions at any length or format — longer or multi-scene pieces, brand / sizzle reels, montages, title cards, static loops, and freeform compositions. Input- and length-agnostic. If a specialized workflow clearly fits the input — a marketed product, a…
motion-graphics
Use when the user wants a short, design-led motion graphic where motion is the message: kinetic typography, stat or number count-up, chart/data-viz hit, logo sting, brand lockup, lower-third, callout, social overlay, animated headline/tweet/news item, motion poster, or quick captured-page highlight. Usually under 10s…
file-issue
Turn a rough idea, a bug, or a batch of unsolved problems into well-structured GitHub issue(s) and file them with gh, auto-classifying type + labels from the content (recommend, then confirm) and following Rove's conventions (beginner-friendly framing, concrete file pointers, an acceptance checklist, zero AI/Anthropic…
release
Autonomously cut a Rove (@sma1lboy/rove) release end-to-end — detect the semver bump from pending changesets (flagging an upstream minor you didn't intend), run the release gates, bump/tag/push via scripts/release.sh, then poll the GitHub Actions Release workflow with gh until npm publish completes, diagnosing CI…