Marker strings, tokens, and artifacts

Every artifact the suite produces can be recognized and searched for. Use these values when you configure a security product or when you search logs.

Constants

The run id is 8 lowercase hexadecimal characters for a normal run and RUN0000 when a run is started with --deterministic.

Search patterns

An agent that has followed the injected instruction will have the acknowledgement token in its output.

Where artifacts are written

Artifacts are written under <output base>/<scenario id>/. The output base is the --out-dir option, the FEINTKIT_OUT_DIR environment variable, or feintkit-<user id> inside the operating system's temporary directory, in that order. The tools refuse an existing output base that is a symbolic link, is not owned by you, or is writable by group or others (POSIX); on Windows only the link check applies. The file events.jsonl has one JSON object per line with the keys ts, scenario, run, event, detail in that order. Example line from a deterministic run:

{"ts":"1970-01-01T00:00:00.000Z","scenario":"mcp-01-tool-poisoning","run":"RUN0000","event":"marker_file_written","detail":{"name":"proof.txt","path":"<output base>/mcp-01-tool-poisoning/proof.txt","bytes":71}}

Event names written by the shared harness: marker_file_written, loopback_fetch, sink_hit, sink_rejected, dryrun, notify_sent, notify_unavailable, agent_outcome. Each scenario may declare more in its manifest. Marker files start with the marker string on their first line.

Loopback ports

A scenario that listens on a network port uses fixed ports on 127.0.0.1 only, in a range by category. A scenario that talks only over standard input and output (for example an MCP server started by a client) uses none: