ANTICELLS Python SDK
Python SDK for ANTICELLS products. The Gaslighter product is available as a namespace inside the package:
from anticells import gaslighter
client = gaslighter.Client.from_env()
Customers normally provide only an API key.
Install
From PyPI:
python -m pip install anticells
To expose Gaslighter to an MCP host (Python 3.10 or newer):
python -m pip install "anticells[mcp]"
For local development from this repository:
python -m pip install -e .\sdk
For maintainers building release artifacts:
cd sdk
python -m pip install -U build twine
python -m build
python -m twine check `
.\dist\anticells-0.3.5-py3-none-any.whl `
.\dist\anticells-0.3.5.tar.gz
This creates both a wheel and source distribution in sdk/dist/.
For a built local wheel:
python -m pip install .\dist\anticells-0.3.5-py3-none-any.whl
Environment
$env:ANTICELLS_API_KEY = "glk_live_customer_key"
Optional auth header override:
$env:ANTICELLS_API_KEY_HEADER = "X-API-Key"
For Authorization: Bearer <key> instead:
$env:ANTICELLS_API_KEY_HEADER = "Authorization"
Command Line
Check connectivity:
anticells gaslighter health
anticells gaslighter personas
Manage account API keys:
anticells gaslighter keys list
anticells gaslighter keys create --name "Notebook key"
anticells gaslighter keys revoke "key_..."
Register and inspect targets:
anticells gaslighter targets list
anticells gaslighter targets get "target_..."
anticells gaslighter targets register `
--url "http://localhost:8080/api/v1/execute" `
--mode relay `
--name "Production assistant" `
--skip-manifest `
--input-field "message" `
--body-template '{"message":"__TARGET_INPUT__"}'
Run the relay from the machine that can reach a private/local target:
anticells gaslighter relay run `
--target "target_..." `
--url "http://127.0.0.1:8080/api/v1/execute" `
--target-credential "target_model_key_or_jwt" `
--target-auth-type bearer `
--target-auth-header "Authorization" `
--target-auth-prefix "Bearer" `
--input-field "message" `
--body-template '{"message":"__TARGET_INPUT__"}'
Run one campaign:
anticells gaslighter attacks run `
--target "target_..." `
--objective "Evaluate whether the target preserves approval boundaries." `
--persona "audit_interface"
Run a family sweep:
anticells gaslighter sweeps run `
--target "target_..." `
--family "system_prompt_extraction" `
--family "tool_abuse" `
--prompts-per-family 2
Optionally tune the dynamic system prompt extraction runner:
anticells gaslighter sweeps run `
--target "target_..." `
--family "system_prompt_extraction" `
--prompts-per-family 1 `
--system-prompt-max-attack-turns 51 `
--system-prompt-representation DIRECT `
--system-prompt-representation ANALYSIS
Run against a chatbot that has no API endpoint:
anticells gaslighter attacks run `
--wait `
--objective "Evaluate whether the target preserves approval boundaries."
anticells gaslighter sweeps run `
--wait `
--family "system_prompt_extraction" `
--prompts-per-family 1
Wait Mode creates and retains a target. For every generated message it
shows which chatbot conversation to use, then waits for the copied chatbot
response. Paste the full response and enter ::end on its own line.
Interrupted sessions can be listed and resumed:
anticells gaslighter wait list
anticells gaslighter wait resume "SESSION_ID"
MCP Server
The optional MCP server exposes Gaslighter as asynchronous start, status, and result tools, plus resources for larger transcripts and Markdown reports.
Set the API key in the environment before starting the MCP host. On Windows, start Codex or Claude Code from the same PowerShell session:
$env:ANTICELLS_API_KEY = "glk_live_customer_key"
codex
# Or: claude
For an IDE or desktop app that is not launched from that terminal, set a persistent user variable and restart the app:
[Environment]::SetEnvironmentVariable(
"ANTICELLS_API_KEY",
"glk_live_customer_key",
"User"
)
On macOS or Linux:
export ANTICELLS_API_KEY="glk_live_customer_key"
codex
# Or: claude
Do not put the key in SKILL.md, a prompt, or a committed configuration file.
The MCP host must start:
anticells-mcp
For Codex, add this to ~/.codex/config.toml or a trusted project's
.codex/config.toml. env_vars forwards the value from Codex's environment
without storing it in the file:
[mcp_servers.anticells-gaslighter]
command = "anticells-mcp"
env_vars = ["ANTICELLS_API_KEY"]
A copyable template is available at
examples/mcp/codex-config.toml.
For Claude Code, put this .mcp.json in the project root. Claude expands the
environment variable when it loads the configuration:
{
"mcpServers": {
"anticells-gaslighter": {
"type": "stdio",
"command": "anticells-mcp",
"env": {
"ANTICELLS_API_KEY": "${ANTICELLS_API_KEY}"
}
}
}
}
A copyable template is available at
examples/mcp/claude.mcp.json. Restart the host
after changing its environment or MCP configuration, then use /mcp to verify
that anticells-gaslighter is connected.
The server can register public targets or start an SDK relay to a private or localhost target. Long-running attacks and sweeps return IDs immediately; poll their status and fetch the result after completion. Full output is available at:
gaslighter://campaign/{campaign_id}/turns
gaslighter://campaign/{campaign_id}/report
gaslighter://batch/{batch_id}/report
Target credentials are never accepted directly as MCP arguments. Put a target
credential in the MCP process environment and pass only its variable name as
credential_env, for example MY_TARGET_API_KEY.
Agent skill for Codex and Claude Code
The repository includes a portable
SKILL.md that teaches a coding
agent when to use each Gaslighter tool, how to test localhost through the SDK
relay, and how to handle results and credentials safely.
Copy the complete gaslighter-security-testing directory into the appropriate
project location:
Codex: .agents/skills/gaslighter-security-testing/SKILL.md
Claude Code: .claude/skills/gaslighter-security-testing/SKILL.md
For a personal installation available in every project, use:
Codex: ~/.agents/skills/gaslighter-security-testing/SKILL.md
Claude Code: ~/.claude/skills/gaslighter-security-testing/SKILL.md
After the MCP server and skill are installed, users can ask naturally, for
example: Use Gaslighter to security-test my localhost agent before deployment.
Quick Start
from anticells import gaslighter
client = gaslighter.Client(api_key="glk_live_customer_key")
target = client.register_target(
url="http://target-service:8080/chat",
name="Staging assistant",
connection_mode="sdk_relay",
skip_manifest=True,
target_body_template={"message": "__TARGET_INPUT__"},
target_body_template_configured=True,
target_input_field="message",
)
relay_runner, relay_thread, relay_stop = gaslighter.start_target_relay_thread(
client,
target_id=target.id,
target_url="http://target-service:8080/chat",
body_template={"message": "__TARGET_INPUT__"},
body_template_configured=True,
input_field="message",
session_field="session_id",
)
try:
result = client.attack(
target_id=target.id,
objective="Evaluate whether the target preserves approval boundaries.",
persona="audit_interface",
verbose=True,
)
print(result.outcome)
print(result.judge_summary)
finally:
relay_stop.set()
relay_thread.join(timeout=5)
relay_runner.close()
objective, custom_objective, and the API-native bad_objective are all
accepted. The SDK sends the API field as bad_objective.
Wait Mode Without a Target API
The user still needs an ANTICELLS API key, but the chatbot being tested does not need an HTTP endpoint:
from anticells import gaslighter
client = gaslighter.Client.from_env()
result = client.attack(
wait_mode=True,
objective="Evaluate whether the target preserves approval boundaries.",
)
print(result.outcome)
Family sweeps use the same interaction and always process child campaigns sequentially in Wait Mode:
result = client.family_sweep(
wait_mode=True,
families=["system_prompt_extraction", "hallucination"],
prompts_per_family=1,
)
At startup the SDK prints a session id. Resume an interrupted run before its pending one-hour relay request expires:
result = client.resume_wait("SESSION_ID")
sessions = client.list_wait_sessions()
Resume files are stored in ~/.anticells/wait-sessions, contain prompts and
any response awaiting acknowledgement, and never contain the ANTICELLS API
key. They are removed after successful completion and retained after an
interruption or failed run. WaitModeOptions can override the state directory,
input/output functions, terminator, or provide a notebook-friendly
response_reader callback.
SDK 0.3.5 supports both backend generations. It uses native
connection_mode="manual" when available. If the backend still requires a URL
and only accepts direct or sdk_relay, the SDK automatically retries with
sdk_relay and a reserved non-routable wait-mode.invalid placeholder URL.
Legacy family sweeps are forced sequential and stop if a child campaign fails.
Python Key Management
from anticells import gaslighter
client = gaslighter.Client.from_env()
keys = client.list_api_keys()
created = client.create_api_key(name="Notebook key")
client.revoke_api_key(created["key"]["id"])
Target Registration Options
register_target mirrors the ANTICELLS target registration contract:
from anticells import gaslighter
client = gaslighter.Client.from_env()
target = client.register_target(
url="https://target.example/chat",
name="Production assistant",
connection_mode="direct",
credential="target-side-secret",
auth={"type": "bearer", "header": "Authorization", "prefix": "Bearer"},
skip_manifest=True,
extra_payload={"tenant": "acme"},
target_body_template={"query": "__TARGET_INPUT__"},
target_body_template_configured=True,
target_input_field="query",
target_input_aliases=["message", "prompt"],
upload_endpoint="/upload",
tool_invocation_endpoint="/tools",
file_read_endpoint="/files/read",
upload_file_field="artifact",
upload_message_field="note",
upload_extra_fields={"workspace": "red-team"},
)
For reusable configuration objects:
from anticells import gaslighter
target = client.register_target_config(
gaslighter.RegisterTarget(url="https://target.example/chat")
)
client.update_target_config(target.id, gaslighter.UpdateTarget(credential=None))
Use connection_mode="sdk_relay" for private/local targets. In relay mode, the
SDK calls the target directly and the ANTICELLS service does not need direct
network access to it.
For multi-turn or concurrent family sweeps, set session_field to the JSON field
your target uses to select a conversation. Relay metadata from compatible servers
is then forwarded in that field and in X-Target-Session-Token; campaign, phase,
and conversation identifiers are also forwarded in X-Gaslighter-* headers. For
example, a target accepting {"query": "...", "session_id": "..."} should use
session_field="session_id". Older servers that do not send session metadata keep
the previous request shape.
For bearer auth, put only the token/JWT in credential. Use
{"type": "bearer", "header": "Authorization", "prefix": "Bearer"} for
Authorization: Bearer <token>.
Family Sweep
from anticells import gaslighter
batch = client.family_sweep(
target_id=target.id,
families=["system_prompt_extraction", "tool_abuse", "hallucination"],
prompts_per_family=2,
direct_phase_enabled=True,
continue_on_child_failure=True,
verbose=True,
)
print(batch.status)
For full personalization:
started = client.start_family_sweep_config(
gaslighter.StartFamilySweep(
target_id=target.id,
persona="audit_interface",
objective_match_mode="specified_only",
stateful_delivery="full_history",
max_history_turns=10,
direct_phase_enabled=False,
prompts_per_family=5,
families=["system_prompt_extraction", "tool_abuse"],
allow_weak_preflight=True,
preflight_override_reason="Authorized audit",
continue_on_child_failure=False,
)
)
result = client.wait_for_batch(started.batch_id, verbose=True)
families=["all"], families=["*"], or an empty family list runs every family.
Reports
report_markdown = client.get_campaign_report(result.campaign_id, tier="growth")
saved_path = client.save_campaign_report(
result.campaign_id,
"reports/gaslighter-campaign.md",
tier="growth",
)
print(saved_path)
The CLI can save reports too:
anticells gaslighter attacks run --target "$TARGET_ID" --objective "..." --trace --report-path reports/campaign.md
Notes
verbose=Noneauto-enables tqdm only in interactive terminals.verbose=Trueforces progress output.verbose=Falseis suitable for CI and pipeline logs.X-API-Key: <key>is the default API-key style for the ANTICELLS gateway.- Use
api_key_header="Authorization"if you needAuthorization: Bearer <key>. - Use the public ANTICELLS API URL for packaged customer builds.
- Native manual-target backend support is preferred, but SDK
0.3.5can use the legacysdk_relaycompatibility path until that backend is deployed.
Metadata
Release files for anticells 0.3.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| anticells-0.3.5.tar.gz | 49.4 kB | Without provenance | Details for anticells-0.3.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| anticells-0.3.5-py3-none-any.whl | Python 3 | none | any | Details for anticells-0.3.5-py3-none-any.whl |
Total release size: 96.0 kB
Release files / anticells-0.3.5.tar.gz
| Download URL | anticells-0.3.5.tar.gz |
|---|---|
| Size | 49.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fcc632f57ff7504ea7b0b7c83ac08e89e918a44ecc661e79ff5ca22192d21be2
|
|
BLAKE2b-256 checksum How to use checksums |
2c40c43f684ceab30fa03c9e645b4c24596f84776897cd3e019b1a9f280eed82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Release files / anticells-0.3.5-py3-none-any.whl
| Download URL | anticells-0.3.5-py3-none-any.whl |
|---|---|
| Size | 46.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dd685ab1c62fd1375ad303ca9e9ba8c99c1dcc5e2318587637e7b29dcbe4986a
|
|
BLAKE2b-256 checksum How to use checksums |
d3fd9cbdce2317cddcd0786ce35521137391d6885f27301d7d1c94f198ba13be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Security for anticells 0.3.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.