Automated recon
Enumerates the target's endpoints, forms and login entry points.
cmdcmd.jpEarly access
cmd is an AI agent that runs penetration tests on its own. It actually attempts attacks and finds the weaknesses that can really be exploited.
It can be triggered from CI/CD, with no expert booking required.
Each finding lists its risk level, reproduction steps and a suggested fix.
Before a test, cmd verifies that the domain is yours. If verification fails, the test does not start.
You pay for the tokens a test actually consumes.
HOW IT WORKS
Four stages, from ownership verification to the report.
This flow is an architectural sketch. See the official documentation for details.
COMPARE
cmd suits routine verification after each release. For complex business-logic flaws, we still recommend verification by INAZUMA experts.
| Vulnerability scan | INAZUMA expert pentest | cmd AI pentest | |
|---|---|---|---|
| Run by | A scanning tool | Security experts | AI Agent |
| Method | Matches known vulnerability signatures | Tests with an attacker's methods | Maps the target, then attempts attacks to confirm exploitability |
| When it runs | On a schedule | By appointment, scheduled by scope | After each release, triggered from CI/CD |
| Best for | Finding known weaknesses broadly | In-depth verification before launch or after major changes | Routine verification after each release |
| Billing | — | Quoted by scope; the first test is free | By token usage |
FEATURES
Feature list includes planned items
Enumerates the target's endpoints, forms and login entry points.
Tests whether login mechanisms and access controls can be bypassed.
Tests for SQL injection, command injection and related flaws.
Runs from the command line as a step in the release pipeline.
Lists findings, risk levels, reproduction steps and suggested fixes.
Confirms before each run that the target belongs to the requester.
USAGE
One command sets the target and starts the test; the report is written as an HTML file. Suited to release pipelines.
$ cmd pentest --target https://staging.example.com Sample
Add targets, start tests and read reports in the browser.
Go to cmd.jpPRICING
cmd is billed by the number of tokens consumed during a test. A wider scope and more checks mean higher usage. Unit price not yet published
FAQ
A vulnerability scan matches known vulnerability signatures. cmd actually attempts the attack, confirms whether the weakness is exploitable, and includes reproduction steps in the report.
Not entirely. cmd suits routine verification after each release. Complex business-logic flaws and items that need deeper verification can be handed to INAZUMA experts.
No. Ownership must be verified before a run, and targets that fail verification are not tested.
We recommend running against staging first, then deciding whether to run against production once you have reviewed the results.
By the number of tokens a test consumes. The unit price has not been published yet; during early access, please ask by email.
cmd is in early access. Apply by email and we will reply with the scope and timing we can offer.