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/crestapps/crestapps.agentskills/crestapps-core-document-processingnpx skills add CrestApps/CrestApps.AgentSkills --skill crestapps-core-document-processinggit clone --depth 1 https://github.com/CrestApps/CrestApps.AgentSkillsWhat 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.00026 | $0.00687 |
| Opus 5 | $0.00013 | $0.00344 |
| Sonnet 5 | $0.00005 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
crestapps-core-document-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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CrestApps.Core Document Processing - Prompt Templates
Add Document Processing
You are a CrestApps.Core expert. Generate code and guidance for document ingestion and document RAG in CrestApps.Core.
Guidelines
- Use
CrestApps.Core.AI.Documentsfor the document pipeline. - Add OpenXml and Pdf support explicitly because they are opt-in packages.
- Add Markdown normalization explicitly when Markdig-backed normalization is needed.
- Provide stores on the document-processing builder.
- Use
AddReferenceDownloads()plusAddDownloadAIDocumentEndpoint()when citations should become downloadable links. AddChatApiEndpoints()is internal MVC and Blazor sample-host composition. Custom hosts should mapAddDownloadAIDocumentEndpoint()directly and add their own chat and upload endpoints as needed.
Builder Registration
builder.Services.AddCrestAppsCore(crestApps => crestApps
.AddAISuite(ai => ai
.AddMarkdown()
.AddChatInteractions()
.AddDocumentProcessing(documentProcessing => documentProcessing
.AddEntityCoreStores()
.AddOpenXml()
.AddPdf()
.AddReferenceDownloads()
)
.AddOpenAI()
)
.AddEntityCoreSqliteDataStore("Data Source=app.db")
);
app.AddDownloadAIDocumentEndpoint();
AddDownloadAIDocumentEndpoint() maps GET ai/documents/{documentId}/download and authorizes access to the referenced document. It is the shared document endpoint; the sample hosts' chat endpoints are not required to register it.
Built-in Reader Coverage
| Reader | Formats |
|---|---|
| Plain text reader | .txt, .md, .json, .xml, .html, .htm, .log, .yaml, .yml, .csv |
| OpenXml reader | .docx, .pptx, .xlsx |
| Pdf reader | .pdf |
Built-in Document Tools
Document retrieval
SearchDocumentsTool— semantic/keyword search across ingested documents.ReadDocumentTool— reads the full text of an ingested document.GetDocumentMetadataTool— returns stored metadata for a document.InspectImageTool— inspects/describes an image document.
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 · 77 lines · 26 tokens per session scan A 42631a1ee929
crestapps-core-document-processing is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 4d ago), licensed MIT. It adds 26 tokens to every session and 687 once invoked, about $0.0001 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-30.
Other skills, from other repositories
azure-openai-to-responses
Migrate Python apps from Azure OpenAI Chat Completions to the Responses API. Covers AzureOpenAI/AsyncAzureOpenAI client migration to the v1 endpoint, streaming, tools, structured output, multi-turn, EntraID auth, and model compatibility checks. Python-focused, Azure OpenAI-specific. USE FOR: migrate to responses API…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
mpg-migration
Handles Azure SDK for .NET management-plane migrations from AutoRest/Swagger to TypeSpec; use for MPG, mgmt migration, or Azure.ResourceManager. migration requests.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…