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/paramountsoftware/ms-access-ai-skill/ms-access-vcsnpx skills add paramountsoftware/ms-access-ai-skill --skill ms-access-vcsgit clone --depth 1 https://github.com/paramountsoftware/ms-access-ai-skillWrote 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/paramountsoftware/ms-access-ai-skill/ms-access-vcs)<a href="https://agentmods.dev/skills/paramountsoftware/ms-access-ai-skill/ms-access-vcs"><img src="https://agentmods.dev/badge/skills/paramountsoftware/ms-access-ai-skill/ms-access-vcs.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.00078 | $0.01263 |
| Opus 5 | $0.00039 | $0.00632 |
| Sonnet 5 | $0.00016 | $0.00253 |
| Haiku 4.5 | $0.00008 | $0.00126 |
Grade A, and why
ms-access-vcs 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microsoft Access VCS Project Guide
Rules and gotchas for programmatically editing Access objects exported by VCS 4.x. Violations cause silent corruption or Error 2128 on import via LoadComponentFromText.
Reference Files
Read the relevant reference file before working on a specific object type:
| When working on... | Read this reference |
|---|---|
Form .bas layout or form controls |
references/forms.md |
Report .bas layout, sections, or sorting/grouping |
references/reports.md |
| Images in forms or reports (add, replace, convert from OLE) | references/images.md |
| Conditional formatting (forms or reports) | references/conditional-formatting.md |
Queries (.bas + .sql) |
references/queries.md |
| Tables, relationships, or ODBC connections | references/tables-and-relationships.md |
VBA modules (.bas) or code-behind (.cls) |
references/vba.md |
| Project config files (vcs-options, vcs-index, etc.) | references/project-config.md |
| Macros, shared images, or import/export specs | references/other-objects.md |
Project Overview
A VCS-exported Access project lives in <DatabaseName>.accdb.src/. The directory name must match the .accdb filename with .src appended.
File Pairing Rules
| Object Type | Files | Notes |
|---|---|---|
| Form | .bas + optional .cls + optional .json |
.bas = layout, .cls = VBA code-behind (omitted if no code), .json = print settings |
| Report | .bas + optional .cls + optional .json |
Same binary text format as forms, .cls = VBA code-behind (uncommon but valid), .json = print settings |
| Query | .bas + .sql |
.bas = metadata/designer state, .sql = SQL text. Always paired |
| Module | .bas |
Standard VBA module |
| Relationship | .json |
Foreign key definition, join type, referential integrity |
| Linked Table | .json |
Connection string, source table, attributes |
| Local Table | .xml |
XSD schema defining columns, data types, indexes. For tables stored inside the .accdb |
| Macro | .bas |
Access macro actions (not VBA). Simpler binary text format |
| Shared Image | .json + image file |
.json = metadata (name, extension, hash), paired with actual image file (.png, .jpg, etc.) |
| Import/Export Spec | .json |
Column definitions, delimiters, data types |
| Theme | .thmx |
Office theme (binary OOXML archive — do not edit) |
What ships with it
10 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.
- LICENSE 1.1 KB
- references/conditional-formatting.md 7.2 KB
- references/forms.md 18 KB
- references/images.md 10 KB
- references/other-objects.md 2.1 KB
- references/project-config.md 14 KB
- references/queries.md 2.6 KB
- references/reports.md 11 KB
- references/tables-and-relationships.md 7.8 KB
- references/vba.md 3.0 KB
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 · 79 lines · 78 tokens per session scan A cbd1a63b1707
ms-access-vcs is a skill published in the GitHub repository paramountsoftware/ms-access-ai-skill (19 stars, last pushed 24d ago), licensed MIT. It adds 78 tokens to every session and 1,263 once invoked, about $0.0004 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
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
debugging
How to debug tursodb using Bytecode comparison, logging, ThreadSanitizer, deterministic simulation, and corruption analysis tools.
sdk-design
Doctrine for designing and evolving any SDK Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface…
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.