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 skills add EvilFreelancer/secs --skill maintaining-engagement-stategit clone --depth 1 https://github.com/EvilFreelancer/secsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/evilfreelancer/secs/maintaining-engagement-state)<a href="https://agentmods.dev/skills/evilfreelancer/secs/maintaining-engagement-state"><img src="https://agentmods.dev/badge/skills/evilfreelancer/secs/maintaining-engagement-state.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00100 | $0.02585 |
| Opus 5 | $0.00050 | $0.01293 |
| Sonnet 5 | $0.00020 | $0.00517 |
| Haiku 4.5 | $0.00010 | $0.00259 |
Grade A, and why
maintaining-engagement-state 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 8d 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.
This is a copy
100% identical to maintaining-engagement-state — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintaining Engagement State
An engagement lasts weeks. A session does not. The gap between those two facts is where work gets repeated, findings lose their evidence, credentials become unattributable, and artifacts get left on production because nobody wrote down that they were placed.
This is not administrative overhead bolted onto the real work. Provenance is what makes a finding reportable, and the artifact register is what makes cleanup possible. Neither can be reconstructed afterwards from terminal scrollback.
Assume everything not written to the record is lost: not merely forgotten, but silently lost, so the next session confidently redoes it or contradicts it.
When to Use
- Any engagement or investigation continuing past a single sitting
- Resuming after a break, or picking up someone else's work
- Approaching a context boundary with unrecorded state
- Handing off between analysts, shifts, or teams
- Before running anything that writes to a target
- When you cannot answer "which host did this credential come from?"
When NOT to Use
- Writing the client-facing deliverable — use
reporting-security-findings; this skill produces the raw material that skill consumes - Deciding whether a finding is real — that is the relevant testing or analysis skill; record the outcome here either way
- Chain of custody for evidence that may reach court — legal custody has
formal requirements beyond this; use
responding-to-incidentsand follow the organisation's counsel - A single self-contained task finished in one sitting with nothing left on target
The Six Records
Keep these in one file, in the repository or case folder, updated as you go — not reconstructed at the end.
1. Scope and authorization
In-scope targets and explicit exclusions, the testing window, the named contact, and where the authorization letter lives. Copy the exclusions verbatim; paraphrasing scope is how people test the wrong estate.
Record one more field, because "in scope" and "reachable" are different questions. Egress mode says what this engagement is allowed to talk to:
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.
- 8d ago First seen · 232 lines · 100 tokens per session scan A 30cde0fdd64b
maintaining-engagement-state is a skill published in the GitHub repository EvilFreelancer/secs (10 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 100 tokens to every session and 2,585 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to maintaining-engagement-state, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
knowledge-management
../../../governance/knowledge-management/SKILL.md.
analyzing-memory-forensics-with-lime-and-volatility
Performs Linux memory acquisition using LiME (Linux Memory Extractor) kernel module and analysis with Volatility 3 framework. Extracts process lists, network connections, bash history, loaded kernel modules, and injected code from Linux memory images. Use when performing incident response on compromised Linux systems.
aatmf-t04-memory-manipulation
AATMF T4 — Multi-Turn & Memory Manipulation. Persistent memory injection, conversation-state poisoning, cross-session contamination, ghost-context leak.
exploiting-format-string-vulnerabilities
Methodology for exploiting format string bugs where attacker-controlled data reaches the format argument of printf-family functions, enabling stack/memory disclosure (info leaks for ASLR/PIE/canary defeat) and arbitrary write primitives (%n) to hijack control flow via GOT/.finiarray overwrites.
Blue Team Defense & Hardening
System hardening, detection engineering, security baseline monitoring, patch management, defense-in-depth architecture, and security posture improvement.
analyzing-slack-space-and-file-system-artifacts
Examine file system slack space, MFT entries, USN journal, and alternate data streams to recover hidden data and reconstruct file activity on NTFS volumes.