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-data-storagenpx skills add CrestApps/CrestApps.AgentSkills --skill crestapps-core-data-storagegit clone --depth 1 https://github.com/CrestApps/CrestApps.AgentSkillsWrote 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/crestapps/crestapps.agentskills/crestapps-core-data-storage)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/crestapps-core-data-storage"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/crestapps-core-data-storage.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 | $0.00026 | $0.00481 |
| Opus 5 | $0.00013 | $0.00241 |
| Sonnet 5 | $0.00005 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
crestapps-core-data-storage 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 5d 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.
What it actually says
CrestApps.Core Data Storage - Prompt Templates
Add Durable Storage
You are a CrestApps.Core expert. Generate code and guidance for storage registration in CrestApps.Core.
Guidelines
- Pick Entity Framework Core or YesSql based on the host architecture.
- Register the data store first, then add per-feature stores.
- Keep storage registration close to the feature that needs it so required stores stay explicit.
- Do not assume one global storage registration covers every feature automatically.
- YesSql requires an explicit backing store: call
AddYesSqlDataStore(configuration => configuration.UseSqLite(...))(or another YesSql provider) to create theIStore, just as Entity Framework Core requiresAddEntityCoreSqliteDataStore(...). The per-featureAddYesSqlStores()calls do not create the store by themselves.
Entity Framework Core Example
builder.Services.AddCrestAppsCore(crestApps => crestApps
.AddAISuite(ai => ai
.AddEntityCoreStores()
.AddOpenAI()
.AddChatInteractions(ci => ci.AddEntityCoreStores())
.AddDocumentProcessing(dp => dp
.AddEntityCoreStores()
.AddOpenXml()
.AddPdf()
)
.AddAIMemory(memory => memory.AddEntityCoreStores())
)
.AddIndexingServices(indexing => indexing.AddEntityCoreStores())
.AddEntityCoreSqliteDataStore("Data Source=App_Data\\crestapps.db")
);
YesSql Example
builder.Services.AddCrestAppsCore(crestApps => crestApps
.AddAISuite(ai => ai
.AddYesSqlStores()
.AddOpenAI()
.AddChatInteractions(ci => ci.AddYesSqlStores())
.AddDocumentProcessing(dp => dp
.AddYesSqlStores()
.AddOpenXml()
.AddPdf()
)
.AddAIMemory(memory => memory.AddYesSqlStores())
)
.AddYesSqlDataStore(configuration => configuration
.UseSqLite("Data Source=App_Data\\crestapps.db;Cache=Shared")
)
);
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.
- 5d ago First seen · 60 lines · 26 tokens per session scan A 131704cdb3e4
crestapps-core-data-storage is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 7d ago), licensed MIT. It adds 26 tokens to every session and 481 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
amazon aurora dsql
Deprecated compatibility redirect for Aurora DSQL guidance. Use when a request concerns DSQL, Aurora DSQL, distributed SQL, DSQL schemas, migrations, queries, authentication, performance, or application development.
solr-semantic-search
To build Solr phrase-tagging semantic search: concept tagging, taxonomy, graph paths.
dv-query
Bulk reads, multi-page iteration, and analytics over Dataverse data. Use when the user wants to read, list, filter, aggregate, group, join, or analyze records — including pandas DataFrame workflows and notebook exploration.
solr-schema
To design and audit Solr schemas: field types, analyzers, docValues, solrconfig.
npgsqlrest
Build and modify REST APIs with NpgsqlRest — exposing PostgreSQL as HTTP endpoints from two sources (database functions/procedures/tables/views, and plain .sql files), driven by SQL comment annotations (no C# needed). Use when working in an NpgsqlRest project: writing or changing endpoint SQL (functions or .sql…
odoo-data-quality-gate
Audit an Odoo database's data quality with evidence before trusting AI answers, importing, or migrating — duplicates, missing required values, orphaned references, format anomalies — and drive remediation through odoo-mcp's gated write workflow. Use when the user asks to "check data quality", "clean up data", "prepare…