Slack Reference
Slash commands, conversation patterns, and everything Cygent responds to in Slack
Everything you can say to Cygent from Slack, in one place. Most of your day-to-day will be @mention + natural language — slash commands are for when you want a form with confirmation.
Slash commands
Slash commands are structured actions with a confirmation dialog before they run. Useful when you want to double-check scope before committing Cygent's time.
| Command | What it does |
|---|---|
/cygent-audit | Start an audit. Opens a modal to pick the project, branch, and scope (files or contracts). |
/cygent-review | Review a specific PR. Takes a PR number or URL. |
/cygent-status | Show what Cygent is currently working on — running audits, in-progress reviews, queued jobs. |
/cygent-findings | Browse findings for a project with severity filters. |
/cygent-notes | View and manage auditor notes for a project. |
/cygent-kb | Search Cygent's knowledge base — your project's past findings, notes, and decisions. |
/cygent-jobs | List recent jobs (audits, reviews, Cygent Code sessions) with status and links. |
Commands without a trailing argument open a modal. Commands with arguments run immediately — e.g. /cygent-review https://github.com/org/repo/pull/42 skips the modal.
Conversation patterns
@mention in a channel
The most common pattern. Tag Cygent, say what you want:
@cygent audit ghostlend
@cygent show me all critical findings in Vault.sol
@cygent review PR #42
@cygent fix finding H-1
@cygent explain why H-2 was marked invalid
Cygent replies in the channel (threaded when the work takes more than a one-shot response).
Threaded follow-ups
Inside a thread started by a Cygent reply, you don't need to re-mention. Cygent already has context:
you (in thread): also add a natspec comment explaining the fix
cygent: Done — amended the PR.
you: run the tests once more
cygent: ✅ all tests pass.
Threads are scoped to a conversation. When you want a fresh context, start a new top-level message with @cygent.
DMs
You can DM Cygent for private work — the same capabilities as channels, no one else sees the conversation. Useful for triaging findings you're not sure about yet.
Multi-action prompts
Combine actions in one message; Cygent plans the sequence:
@cygent create a GitHub issue and open a PR fixing H-1
@cygent review PR #12 and if it's clean, summarize the changes in #eng
@cygent find all findings related to claimReward and mark the invalid ones
Smart interjection
Cygent monitors channels it's in for security-relevant discussions and will chime in when it has something useful to say — a past finding that's relevant, a known pitfall, a missing context the team might want to capture.
It does not reply to every message. An engagement-scoring step decides whether a message warrants a response; most don't. You can dial the threshold in Behavior & Autonomy.
A real example from the walkthrough: a team discussed using "Aave V3 math" for liquidations and deploying on Arbitrum. Cygent replied unprompted, acknowledged the decisions, and added rules to future audits to (a) flag any drift from Aave V3 math, (b) check for sequencer-uptime-oracle handling appropriate to Arbitrum L2.
Auditor notes
Save team decisions as notes so Cygent remembers them across sessions and channels:
@cygent remember that we accepted the risk on H-2 because the token is trusted
@cygent note that withdrawCollateral will eventually migrate to CEI; M-4 is pre-approved
List, search, or delete notes from /cygent-notes or by asking in-channel. Notes are visible to the whole team — they're workspace-wide context, not per-user.
Notifications
Cygent posts unsolicited messages for:
- Audit completions (to the default review channel, or per-project override)
- PR review results (same routing)
- Scheduled task outputs (channel chosen per task)
- Finding alerts when auto-create issues is enabled above a threshold
- Status changes on long-running jobs (audit finished, Battle Mode complete)
Turn individual streams on or off in Settings → Notifications. See Configuring Settings.
Home tab
Clicking Cygent's name in the Slack sidebar opens the Home tab — a dashboard view inside Slack itself:
- Projects — every connected repo with its audit status and last activity
- Recent jobs — the last ~20 audits, reviews, and Cygent Code sessions, with links to detail
- Finding counts — Critical / High / Medium / Low tallies across all projects
- Quick actions — buttons for common actions (run audit, open dashboard, view scheduled tasks)
The Home tab is read-mostly — use @mention or slash commands for actions. It's designed for "what's the security posture right now?" without leaving Slack.