DE//AGENT
Explore
Tutorial Lesson 2 of 10 · The Agentic Series community intermediate

Onboard an agent with the DE Data Toolkit

Onboard an agent onto a data repo with the DE Data Toolkit plugin: the SQL/Spark review skills, the destructive-SQL guard, a secret scanner, and the file/git MCP servers already wired. Learn the three commands and which hooks run underneath.

At a glance

When Onboarding an agent onto a data engineering repo; A starter setup that needs review skills plus guardrails from day one
Where Agentic Data Engineering
Why The starter plugin wires the review skills, the file/git servers and the safety hooks together, so an agent is useful and guarded on day one.

Learning objectives

  • Install the starter plugin for a data repo
  • Use /review-sql and /review-spark on a change
  • Verify guard status before writing

What you need

  • An agent host with plugin support
  • A data repository to review
  • [object Object]

Steps

  1. Install the plugin: `amp plugin add de-agent/de-data-toolkit`. (from plugin-de-data-toolkit )
  2. Confirm what ships — SQL/Spark review skills, the destructive-SQL guard, a secret scanner and the file/git MCP servers. (from plugin-de-data-toolkit )
  3. Run `/review-sql` on a SQL change. (from plugin-de-data-toolkit )
  4. Run `/review-spark` on a PySpark transform. (from plugin-de-data-toolkit )
  5. Run `/guard-status` to check the wired guards. (from plugin-de-data-toolkit )
  6. Note the hooks wired underneath — hook-destructive-sql-guard and hook-secret-scan-commit. (from plugin-de-data-toolkit )

Check yourself

  • `DROP TABLE prod.orders` from the agent is denied and surfaced for confirmation.
  • A staged diff containing a hardcoded `postgresql://user:pass@...` connection string is blocked at commit.

Worked example

Install the plugin — from plugin-de-data-toolkit

amp plugin add de-agent/de-data-toolkit

The three commands — from plugin-de-data-toolkit

/review-sql     # review a SQL change
/review-spark   # review a PySpark transform
/guard-status   # check the wired guards

Destructive SQL guard — what gets denied — from hook-destructive-sql-guard

Destructive statements are denied by default; a DELETE/UPDATE without a WHERE
clause is always denied. Statements on a non-production target can be allowed
with a `--allow-destructive` flag that requires a human confirmation token.

Example: `DROP TABLE prod.orders` from an agent is denied and surfaced for confirmation.

Sourced from

Security scan

Last sweep 2026-10-24: 0 finding(s), 0 marked as examples.

Common gotchas

  • The plugin's permissions are filesystem read-write with network none — it reviews code; it does not query warehouses.
  • A DELETE/UPDATE without a WHERE clause is always denied by the destructive SQL guard.
  • Entropy-based secret detection warns; pattern matches block — a warning is not a pass.

Production considerations

  • Keep hook-secret-scan-commit active on every repo agents commit to.
  • The plugin uses skill-sql-review and skill-spark-data-quality-review — keep them in sync with the plugin.

Diagram

agent + de-data-toolkit
   |
   |- /review-sql --> SQL findings
   |
   |- /review-spark --> transform findings
   |
   |- /guard-status --> guards active
   |
   |- hooks --> destructive SQL denied + secrets blocked at commit

Registry stats

Verification community · Oct 21, 2026
Completeness 81
Trust multiplier ×1.25
Composite 34.15 · adequate
Freshness 3 days since last source check
Difficulty intermediate
Version 0.1.0
License CC-BY-4.0
Security flags none