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 commands/nxtg-ai/forge-plugin/integrategit clone --depth 1 https://github.com/nxtg-ai/forge-pluginWhat 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.00000 | $0.01146 |
| Opus 5 | $0.00000 | $0.00573 |
| Sonnet 5 | $0.00000 | $0.00229 |
| Haiku 4.5 | $0.00000 | $0.00115 |
Grade A, and why
integrate 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 2d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/forge:integrate
Set up third-party service integrations with scaffolded client code, environment variable guides, and connectivity testing.
| Level | L1 Vibe Coder |
| Category | Feature Development |
| Syntax | /forge:integrate [service-name] [--list] [--test] [--scaffold] |
What It Does
/forge:integrate is the integration assistant for connecting your project to external services. It covers version control (GitHub, GitLab), monitoring (Sentry, Datadog), communication (Slack, Discord), databases (PostgreSQL, Redis, MongoDB), and cloud platforms (AWS, GCP, Vercel, Netlify). For each service, it checks your current setup, identifies what is already configured, and provides the exact npm packages, environment variables, configuration code, and testing instructions needed.
The command does not blindly generate boilerplate. It first reads your package.json for existing SDK packages, checks .env and .env.example for existing configuration, and scans src/ for existing integration code. This means it only suggests what is actually missing and avoids duplicating what you already have.
Without this command, integrating a service means reading its documentation, figuring out which SDK to install, creating a client wrapper, setting up environment variables, and writing a connectivity test -- all separately. /forge:integrate packages all of that into a single guided flow.
Syntax & Options
/forge:integrate [service-name] [--list] [--test] [--scaffold]
| Option | Description |
|---|---|
service-name |
The service to integrate (e.g., github, sentry, postgres, vercel) |
--list |
Show all available integration templates organized by category |
--test |
Test connectivity for existing integrations |
--scaffold |
Generate integration boilerplate code (client file, types, environment variables) |
When to Use It
- Adding a new service: Need Sentry for error tracking? Run
/forge:integrate sentryto get the complete setup guide. - Verifying connections: Run
/forge:integrate --testafter configuring environment variables to verify everything connects. - Discovering options: Run
/forge:integrate --listto see all supported services organized by category.
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.
- 2d ago First seen · 112 lines · 0 tokens per session scan A 9cf424abb498
integrate is a command published in the GitHub repository nxtg-ai/forge-plugin (5 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,146 tokens. 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 commands, from other repositories
paul:help
Show available PAUL commands and usage guide.
safe-refactor
Safe refactoring with automated review, testing, and rollback capabilities.
paul:verify
Guide manual user acceptance testing of recently built features.
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
hatch3r-benchmark
Run and analyze performance benchmarks. Compare results against baselines, identify regressions, and produce performance reports.