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/lab94/frenchie-skill/ocrgit clone --depth 1 https://github.com/Lab94/frenchie-skillWhat 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.00000 | $0.00501 |
| Opus 5 | $0.00000 | $0.00251 |
| Sonnet 5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
ocr 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 yesterday.
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.
PUT the file to `upload_url` (e.g. `curl -X PUT -H "Content-Type: application/pdf" -T file.pdf "<upload_url>"`). What it actually says
Convert the file at $ARGUMENTS into Markdown using the Frenchie MCP server.
Hard rule: in HTTP mode, MUST persist the final Markdown to .frenchie/{name}/result.md before concluding the task. This rule does not apply to stdio mode because the local MCP server already writes .frenchie/... automatically.
- Determine transport mode:
- HTTP (MCP configured with
url/serverUrl): NEVER sendfile_path. Callupload_filewithfilename,file_size(bytes),mime_type→ getupload_urlandobject_key. PUT the file toupload_url(e.g.curl -X PUT -H "Content-Type: application/pdf" -T file.pdf "<upload_url>"). Then callocr_to_markdownwithuploaded_file_referenceset toobject_key. - stdio (MCP configured with
command/args): callocr_to_markdownwithfile_pathset to the absolute path
- HTTP (MCP configured with
- If
statusis"done":- stdio mode → the response is metadata-only (
savedTo,wordCount,imageCount). Read the file atsavedTowith your own file tool if the task needs the content; do not re-run the OCR job expecting inline markdown - HTTP mode → continue to step 5 to save results locally before concluding the task
- stdio mode → the response is metadata-only (
- If
statusis"processing", poll withget_job_resultusing the returnedjobIduntil done - If the result has expired, inform the user that the payload is no longer available
- If the result contains
frenchie-result:image references (HTTP mode), callfetch_result_filefor each object_key and save to.frenchie/{name}/where name is the source filename without extension (e.g.report.pdf→.frenchie/report/) - In HTTP mode, rewrite any
frenchie-result:references to local filenames and write the final Markdown to.frenchie/{name}/result.md - If there are no
frenchie-result:references, still write the returned Markdown to.frenchie/{name}/result.md
Supported formats: PDF, PNG, JPG/JPEG, WebP
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.
- yesterday First seen · 21 lines · 0 tokens per session scan A d0da3b4e93d1
ocr is a command published in the GitHub repository Lab94/frenchie-skill (0 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 501 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-31.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.