Borrowing it
Nothing to install: this file belongs to bablsoft/accessflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bablsoft/accessflow/main/.claude/skills/add-engine/SKILL.mdgit clone --depth 1 https://github.com/bablsoft/accessflowWrote 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/bablsoft/accessflow/add-engine)<a href="https://agentmods.dev/skills/bablsoft/accessflow/add-engine"><img src="https://agentmods.dev/badge/skills/bablsoft/accessflow/add-engine/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bablsoft/accessflow/add-engine"><img src="https://agentmods.dev/badge/skills/bablsoft/accessflow/add-engine.svg" alt="Reviewed on agentmods" width="80" 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.00110 | $0.02417 |
| Opus 5.5 | $0.00044 | $0.00967 |
| Sonnet 5.5 | $0.00022 | $0.00483 |
| Haiku 4.5 | $0.00011 | $0.00242 |
Grade A, and why
add-engine 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 1mo 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
add-engine
Adding an engine is ~12 areas of wiring, most of it outside engines/. The plugin itself is the
easy half; the half that gets forgotten is DbType → migration → credential gates → i18n ×7 →
frontend → docs → website → CI matrix.
Read first, in order: docs/15-engine-sdk.md (authoritative —
the SPI surface, QueryEngineContext semantics, and the checklist at its end),
.claude/patterns/engine-plugin.md, and
.claude/patterns/engine-fanout.md.
Inputs
Ask for anything not supplied — do not guess:
- engine id (lowercase; it is simultaneously the folder name, the connector id, and the
engineId()return value — all automation derives from it) - display name, vendor, documentation URL
DbTypevalue (SCREAMING_SNAKE) andcategory—WAREHOUSE|DOCUMENT|KEY_VALUE|WIDE_COLUMN|SEARCH|GRAPH- driver coordinates, or "REST API, no driver" (the
engines/databricks/shape) - default port and default SSL mode
- connection model — host/port/db/user/pass, or cloud credentials (region + keys, service account JSON, workspace host + token)
- a Testcontainers image, or "none" (the Snowflake precedent: unit + mocked-facade tests only)
Pick the closest existing engine and follow it
| Shape | Follow |
|---|---|
| SQL dialect over JDBC | engines/snowflake/ |
| SQL dialect over REST, no vendor driver at all | engines/databricks/ |
| Cloud credentials instead of host/port | engines/dynamodb/ |
| Document | engines/mongodb/ |
| Key-value | engines/redis/ |
| Graph | engines/neo4j/ |
Workflow
1. Build the host jar the plugin compiles against
mvn -f backend/pom.xml install -DskipTests
2. Scaffold engines/<id>/pom.xml
Non-negotiables (copy from the reference engine): its own <version> starting at 1.0.0;
maven.compiler.release 25; a fixed project.build.outputTimestamp; accessflow and slf4j-api
at provided scope; shade with shadedArtifactAttached=true, classifier all, and every
third-party library except the vendor driver relocated under
com.bablsoft.accessflow.engine.<id>.shaded.*; surefire + failsafe wired.
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.
- 1mo ago Changed · +4 lines 1954cd9647ad
- 2mo ago First seen · 178 lines · 110 tokens per session scan A a44ba32b159c
add-engine is a skill published in the GitHub repository bablsoft/accessflow (11 stars, last pushed today), licensed Apache-2.0. It adds 110 tokens to every session and 2,417 once invoked, about $0.0004 per session on Opus 5.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-31.
Other skills, from other repositories
firebase-app-platform
Build and operate apps on Firebase using Auth, Firestore, Cloud Functions, and Hosting. Use when building mobile/web backends with managed services, real-time data sync, or serverless APIs.
design
Design a production-grade, API-first multitenant Spring Boot and PostgreSQL architecture. Use when starting a SaaS, adding tenant isolation, defining environment/account/company boundaries, choosing tenant resolution, designing API keys or browser sessions, modeling hierarchical permissions, planning PostgreSQL RLS…
convex-backend
Build reactive backends with Convex functions, schema validation, auth integration, and deployment workflows. Use when building real-time apps with type-safe server functions and automatic caching.
data-design
Data modeling, schema design, and data architecture.
scalability-review
Scope-aware review of scalability and performance readiness — database indexing and query patterns, N+1 queries, caching strategy, connection pooling, horizontal scalability, statelessness, rate limiting, pagination, background job architecture, and expected-load headroom. Thresholds adapt sharply to the project's…
api-mirror
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.