Apache Tika is a toolkit that reads many kinds of files and extracts their text and descriptive metadata, including from formats such as PDF, PowerPoint, and Excel. Applications and agent pipelines use it to turn documents into content they can process, search, or pass to language models. The catalogue skills provide reusable ways for coding agents to run Tika for file-to-Markdown extraction.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/apache/tikanpx agentmods add skills/apache/tika/update-site-for-releaseWrote 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/apache/tika/update-site-for-release)<a href="https://agentmods.dev/skills/apache/tika/update-site-for-release"><img src="https://agentmods.dev/badge/skills/apache/tika/update-site-for-release/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/apache/tika/update-site-for-release"><img src="https://agentmods.dev/badge/skills/apache/tika/update-site-for-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 264 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Rogue Agent · line 145 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00092 | $0.06154 |
| Opus 5.5 | $0.00037 | $0.02462 |
| Sonnet 5.5 | $0.00018 | $0.01231 |
| Haiku 4.5 | $0.00009 | $0.00615 |
Grade C, and why
update-site-for-release scanned grade C with 2 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 21d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf docs/target/site # Antora never prunes: a stale <old>-SNAPSHOT dir from an earlier build gets published Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code}\n" "https://tika.apache.org/<NEW>/index.html?cb=$(date +%s)" How it starts
The opening of the file, as written. The whole thing — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local override: $TIKA_SKILLS_LOCAL/update-site-for-release/LOCAL.md (default ~/.tika-skills),
read after this file, wins on conflict.
Update the Tika website for a release
Step 17 ("Update Tika site") of the Release Process (https://cwiki.apache.org/confluence/spaces/TIKA/pages/109454070/Release+Process). Assumes the release (tag, artifacts, VOTE, dist promotion) is done; covers the website only.
First: cd $SITE && svn update. The checkout is usually behind (docs
republishes, logo/security edits land between releases); a stale base only
surfaces at the very end, after the 67 MB commit has uploaded, as
E155011 ... is out of date, and the whole transaction rolls back.
Set these first:
$SITE—tika-siteSVN checkout (not git):src/site/(sources) +publish/(generated, SVN-tracked, served;mvn installregenerates it and auto-runssvn add --force publishvia antrun).$SCRATCH— release working dir: unzipped src release,CHANGES-<NEW>.txt, built javadoc.
Scripts: ./scripts/. Local paths + toolchain (Maven binary, JDKs) live in a
private companion skill under ~/.claude/skills/.
[HUMAN] gates — never do these yourself: final
svn commit(outward-facing, irreversible), JIRA "release", s.apache.org shortlink, announce emails. Prepare everything, showsvn status, hand off.
What ships with it
4 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.
- 21d ago Changed · +38 lines scan A → C ce14bd9bffc5
- 1mo ago Changed · +1 lines 43d6137ebdd1
- 1mo ago First seen · 381 lines · 92 tokens per session scan A 76354e126a05
update-site-for-release is a skill published in the GitHub repository apache/tika (4,105 stars, last pushed yesterday), licensed Apache-2.0. It adds 92 tokens to every session and 6,154 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
release-plugin
Prepare and execute a new release for the flutter-intellij plugin, including updating dependencies, compatibility bounds, changelogs, and verification.
changelog-generator
Generate changelogs from git commits. Use when user says "generate changelog", "update changelog", "what changed since last release", or before preparing a new release.
zb-release-pipeline
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb…
shipping-and-launch
Pre-deploy hygiene for a Spring Boot 4 feature — verify gates, capture rollback plan, sign off observability, generate release notes, and stage the rollout. Used by /ship after /review approves the diff. The agent never deploys; it produces the plan a human executes.
changelog-release-notes
A BK-CI release-notes workflow for processing newly added version sections in a changelog. A changelog is a file that records software changes between releases.
pre-release
Runs the pre-release checklist. Sets the readme.txt Stable tag to the version being released, captures every page type (sitemaps, robots, feeds, and the rest of the catalog), and flicks all buttons that the changelog mentions. Use when preparing a release, shipping a WordPress.org update, or when the user asks for the…