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 commands/crisng95/flowkit/fk-gen-text-overlaysgit clone --depth 1 https://github.com/crisng95/flowkitWrote 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/commands/crisng95/flowkit/fk-gen-text-overlays)<a href="https://agentmods.dev/commands/crisng95/flowkit/fk-gen-text-overlays"><img src="https://agentmods.dev/badge/commands/crisng95/flowkit/fk-gen-text-overlays.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.00000 | $0.01457 |
| Opus 5 | $0.00000 | $0.00728 |
| Sonnet 5 | $0.00000 | $0.00291 |
| Haiku 4.5 | $0.00000 | $0.00146 |
Grade A, and why
fk-gen-text-overlays scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://127.0.0.1:8100/api/videos/<VID> How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fk-gen-text-overlays — Generate Text Overlays from Narrator Text
Analyze narrator text for each scene and extract key data points (dates, locations, statistics, milestones, costs) to create text_overlays.json for /fk-concat-fit-narrator.
Usage: /fk-gen-text-overlays <video_id> [--language vi]
video_id— the video to generate overlays for--language— target language code (default: auto-detect from narrator text). All overlay text MUST be in this language with proper diacritics/characters.
Step 1: Load project, video, scenes
curl -s http://127.0.0.1:8100/api/videos/<VID>
# Get project_id
curl -s http://127.0.0.1:8100/api/projects/<PID>
curl -s "http://127.0.0.1:8100/api/scenes?video_id=<VID>"
curl -s http://127.0.0.1:8100/api/projects/<PID>/output-dir
Sort scenes by display_order. Note OUTDIR from output-dir response.
Step 2: Detect target language
If --language not provided, auto-detect from the first scene's narrator_text:
- Vietnamese diacritics (ắ, ề, ổ, ử, ơ, etc.) →
vi - Spanish characters (ñ, á, é, etc.) →
es - Default →
en
CRITICAL RULE: All overlay text MUST be written in the detected language with full diacritics and proper characters. NEVER strip diacritics or romanize.
Examples:
- Vietnamese: "Chiến dịch Tapalpa" NOT "Chien dich Tapalpa"
- Vietnamese: "Tiền thưởng" NOT "Tien thuong"
- Spanish: "Operación Tapalpa" NOT "Operacion Tapalpa"
Step 3: Analyze each scene's narrator text
For each scene with narrator_text, extract data points that fit these overlay categories:
Overlay styles
| Style | What to extract | Color |
|---|---|---|
date |
Dates, times, timestamps, time references | Cyan |
name |
Locations, operation names, people, organizations | White |
stat |
Numbers, quantities, distances, technology milestones | White |
cost |
Casualties, monetary values, damage, human cost | Gold |
Extraction rules
- NOT every scene needs overlays. Only add overlays when there's a clear, impactful data point.
- Target ~40-50% of scenes having overlays (e.g., 25-30 out of 60 scenes).
- Max 2 text items per scene — one primary, one secondary.
- Keep text SHORT — max 40 characters per line. Abbreviate if needed.
- Prioritize hard data — numbers, dates, names, costs over descriptive text.
- Avoid repeating the same information across adjacent scenes.
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.
- 6d ago First seen · 145 lines · 0 tokens per session scan A 4e7f42d1ca34
fk-gen-text-overlays is a command published in the GitHub repository crisng95/flowkit (625 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,457 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.