Nextjs Data Access Layer
HoangNguyen0403/agent-skills-standard
Build secure, reusable data access patterns with DTOs, taint checks, and colocated authorization in Next.js.
Audit application database access layers for query construction, authorization placement, tenant scoping, transaction boundaries, consistency, credential authority, and observable durable effects.
Install Audit Database Access Layer
$ npx skills add cyberful/cyberful --skill audit-database-access-layer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cyberful/cyberful audit-database-access-layer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cyberful/builtin/skills/audit-database-access-layer .claude/skills/audit-database-access-layer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "audit-database-access-layer" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/audit-database-access-layer into .claude/skills/audit-database-access-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit-database-access-layer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/audit-database-access-layerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cyberful/cyberful --skill audit-database-access-layer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cyberful/cyberful audit-database-access-layer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cyberful/builtin/skills/audit-database-access-layer .agents/skills/audit-database-access-layer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "audit-database-access-layer" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/audit-database-access-layer into .agents/skills/audit-database-access-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit-database-access-layer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cyberful/cyberful --skill audit-database-access-layer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cyberful/cyberful audit-database-access-layer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cyberful/builtin/skills/audit-database-access-layer .cursor/skills/audit-database-access-layer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "audit-database-access-layer" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/audit-database-access-layer into .cursor/skills/audit-database-access-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit-database-access-layer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cyberful/cyberful.git --path cyberful/builtin/skills/audit-database-access-layer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cyberful/cyberful --skill audit-database-access-layer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cyberful/cyberful audit-database-access-layer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cyberful/builtin/skills/audit-database-access-layer .gemini/skills/audit-database-access-layer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "audit-database-access-layer" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/audit-database-access-layer into .gemini/skills/audit-database-access-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit-database-access-layer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cyberful/cyberful audit-database-access-layerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cyberful/cyberful --skill audit-database-access-layer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .github/skills && cp -r skills-src/cyberful/builtin/skills/audit-database-access-layer .github/skills/audit-database-access-layer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "audit-database-access-layer" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/audit-database-access-layer into .github/skills/audit-database-access-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit-database-access-layer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cyberful/cyberful --skill audit-database-access-layer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cyberful/cyberful audit-database-access-layer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cyberful/builtin/skills/audit-database-access-layer .opencode/skills/audit-database-access-layer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "audit-database-access-layer" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/audit-database-access-layer into .opencode/skills/audit-database-access-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit-database-access-layer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
audit-database-access-layer- GitHub stars
- 134
- Token cost
- ~599 tokens
- SKILL.md length
- 180 words
- Files
- 5 (incl. references, assets)
- Skills in repo
- 85
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Audit application database access layers for query construction, authorization placement, tenant scoping, transaction boundaries, consistency, credential authority, and observable durable effects.
- Stored-procedure review
- SKILL.md covers Map each data effect and Confirm a boundary failure
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve ORMs and data access
What it does
Audit Database Access Layer is an agent skill from cyberful/cyberful. Audit application database access layers for query construction, authorization placement, tenant scoping, transaction boundaries, consistency, credential authority, and observable durable effects. Use for ORM, repository, DAO, or stored-procedure review.
Its SKILL.md is about 600 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files and assets (for example `agents/openai.yaml`, `assets/database-boundary-ledger.example.json` and `assets/database-boundary-ledger.schema.json`).
It sits in Databases, covering ORMs and data access and Authorization and RBAC. The repository describes itself as: Cyberful is an open-source AI Red Team for discovering, exploiting, verifying, and remediating vulnerabilities. The licence is AGPL-3.0.
When your agent uses it
- Stored-procedure review
- Tasks that involve ORMs and data access
- Tasks that involve Authorization and RBAC
Example prompts
- “/audit-database-access-layer”
What it can do on your machine
Read from SKILL.md and the folder at commit ec598a6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Audit Database Access Layer loads about 599 tokens when it runs, and up to ~937 if it reads all its reference files. Until then it costs about 71 tokens; SKILL.md has 180 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from cyberful/cyberful at commit ec598a6, republished under its AGPL-3.0 licence (© cyberful). 180 words, ~599 tokens.
Download SKILL.mdSave it as
.claude/skills/audit-database-access-layer/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- audit-database-access-layer
- description
- Audit application database access layers for query construction, authorization placement, tenant scoping, transaction boundaries, consistency, credential authority, and observable durable effects. Use for ORM, repository, DAO, or stored-procedure review.
- metadata.domain
- application-security
- metadata.subdomain
- database-access
- metadata.triggers
- database access layer audit, ORM security review, tenant query scoping, repository authorization audit, transaction boundary review, stored procedure security
- metadata.tags
- database, orm, query-construction, tenant-isolation, transactions, authorization
Audit Database Access Layer
Trace protected data operations from caller intent to committed state. Treat an ORM, query builder, repository, stored procedure, and database policy as separate enforcement boundaries; convenience abstractions do not prove authorization or atomicity.
Map each data effect
Read references/database-boundary-method.md. Populate assets/database-boundary-ledger.example.json under assets/database-boundary-ledger.schema.json. For each read, mutation, bulk operation, background job, and administrative path, record caller identity, tenant source, object selector, query construction, policy location, transaction scope, credential, replica or primary destination, durable effect, and evidence.
Inspect parameter binding, raw fragments, dynamic identifiers, default scopes, eager/lazy loading, joins, row-level security, soft deletes, optimistic locks, retry behavior, connection pooling, migration code, stored procedures, read replicas, caches, and asynchronous writes. Trace whether authorization is evaluated against the same object and state that is later read or mutated.
Confirm a boundary failure
Report only a causal path from reachable input or authority to unintended records, fields, tenants, ordering, or durable state. Separate unsafe syntax from reachable injection, missing application filters from effective database policy, stale reads from unauthorized reads, and a partial failure from a transactionally committed invariant violation.
© cyberful, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references, assets) in cyberful/builtin/skills/audit-database-access-layer of cyberful/cyberful.
- SKILL.md
- agents/openai.yaml
- assets/database-boundary-ledger.example.json
- assets/database-boundary-ledger.schema.json
- references/database-boundary-method.md
Open the folder on GitHubat commit ec598a6
Compare with similar skills
Audit Database Access Layer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Audit Database Access Layer this skillcyberful/cyberful | 134 | — | ~599 | Automated safety check: Pass | AGPL-3.0 | |
| Nextjs Data Access LayerHoangNguyen0403/agent-skills-standard | 570 | — | ~581 | Automated safety check: Pass | MIT | |
| Database Migration Patterns with RLSbybren-llc/safe-agentic-workflow | 421 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Content Create Hero Imageprisma/web | 1.1k | — | ~6.9k | Automated safety check: Pass | None | |
| Sea Orm 2FlyinPancake/yoink | 112 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Prisma Client APIcurvenote/curvenote | 169 | 2 repos | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
Database Migration Patterns with RLS
bybren-llc/safe-agentic-workflow
Database migration creation with mandatory RLS policies and ARCHitect approval workflow. Use when creating migrations, adding tables with RLS, updating ORM…
- Official
Content Create Hero Image
prisma/web
A skill your agent uses when the operator wants a hero or meta image for a Prisma blog post; asks to create or generate a blog hero, cover, social card, Open Graph, or YouTube image; mentions cover…
Sea Orm 2
FlyinPancake/yoink
Expert guidance for SeaORM 2.0, Rust's async ORM with strongly-typed columns, nested ActiveModels, Entity Loader API, and entity-first workflow.
Prisma Client API
curvenote/curvenote
Prisma Client API reference covering model queries, filters, operators, and client methods.
DB Migrate
simstudioai/sim
Author or review a Drizzle DB migration for zero-downtime safety — expand/contract phasing, backward-compatibility with the deployed app version, and writing the -- migration-safe acknowledgment the…
More from cyberful/cyberful
All 85 skills in this repoAudit Infrastructure As Code
cyberful/cyberful
Audit infrastructure-as-code artifacts for unsafe defaults, policy gaps, privilege exposure, control drift, and deployment-impact evidence.
Audit Kubernetes Policy Enforcement
cyberful/cyberful
Audit Kubernetes admission and policy-as-code enforcement against local workload manifests, exception paths, namespace scope, and deployment evidence.
Audit Pci Dss Penetration Test Evidence
cyberful/cyberful
Audit PCI DSS penetration-test methodology, scope, internal and external reports, segmentation results, tester independence, remediation, retesting, retention, and multi-tenant support evidence.
Operate Content Discovery
cyberful/cyberful
Design and interpret advanced content discovery with ffuf and complementary web fuzzers.
Operate Network Recon
cyberful/cyberful
Build a high-fidelity network and service inventory using Nmap, Masscan, packet capture, DNS, and protocol-specific follow-up.
Operate Sast Toolchain
cyberful/cyberful
Operate Semgrep and source-oriented static analysis as a hypothesis, coverage, and regression system during advanced code audits.
Related
Categories
Questions about Audit Database Access Layer
What does Audit Database Access Layer do?
Audit application database access layers for query construction, authorization placement, tenant scoping, transaction boundaries, consistency, credential authority, and observable durable effects. Audit Database Access Layer is an agent skill from cyberful/cyberful. Audit application database access layers for query construction, authorization placement, tenant scoping, transaction boundaries, consistency, credential authority, and observable durable effects.
When should I use Audit Database Access Layer?
Audit Database Access Layer fits situations like: stored-procedure review; tasks that involve ORMs and data access; tasks that involve Authorization and RBAC.
How do I install Audit Database Access Layer in Claude Code?
Run `npx skills add cyberful/cyberful --skill audit-database-access-layer -a claude-code`. Or copy the skill folder (cyberful/builtin/skills/audit-database-access-layer in cyberful/cyberful) into .claude/skills/audit-database-access-layer in your project. Claude Code loads it when a task matches its description.
How do I install Audit Database Access Layer in Codex?
Run `npx skills add cyberful/cyberful --skill audit-database-access-layer -a codex`. Or copy the skill folder (cyberful/builtin/skills/audit-database-access-layer in cyberful/cyberful) into .agents/skills/audit-database-access-layer in your project. Codex loads it when a task matches its description.
Can I use Audit Database Access Layer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cyberful/cyberful --skill audit-database-access-layer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/audit-database-access-layer, .gemini/skills/audit-database-access-layer, .github/skills/audit-database-access-layer and .opencode/skills/audit-database-access-layer in your project.
What does Audit Database Access Layer need to run?
SKILL.md names no scripts, command-line tools or credentials: Audit Database Access Layer is instructions for the agent only.
Does Audit Database Access Layer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Audit Database Access Layer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Audit Database Access Layer use?
Audit Database Access Layer is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Audit Database Access Layer use?
About 599 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 338 tokens, read only when the agent opens those files.
What are the alternatives to Audit Database Access Layer?
Skills that share tags, products or a category with Audit Database Access Layer: Nextjs Data Access Layer (HoangNguyen0403/agent-skills-standard, 570 stars), Database Migration Patterns with RLS (bybren-llc/safe-agentic-workflow, 421 stars), Content Create Hero Image (prisma/web, 1.1k stars) and Sea Orm 2 (FlyinPancake/yoink, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Audit Database Access Layer?
cyberful (a GitHub organization) maintains it in cyberful/cyberful, which has 134 GitHub stars. The repository holds 85 skills in this directory. The repository was last updated on August 24, 2026.
Source: cyberful/cyberful on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.