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 phuonghx/aim-cli --skill red-team-tacticsgit clone --depth 1 https://github.com/phuonghx/aim-cliWrote 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/phuonghx/aim-cli/red-team-tactics)<a href="https://agentmods.dev/skills/phuonghx/aim-cli/red-team-tactics"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/red-team-tactics/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/phuonghx/aim-cli/red-team-tactics"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/red-team-tactics.svg" alt="Reviewed on agentmods" width="80" 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.00089 | $0.01086 |
| Opus 5.5 | $0.00036 | $0.00434 |
| Sonnet 5.5 | $0.00018 | $0.00217 |
| Haiku 4.5 | $0.00009 | $0.00109 |
Grade A, and why
red-team-tactics scanned grade A with 1 finding 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 1mo 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
On **Linux**, look for SUID binaries that run as a more privileged owner, sudo rules that permit unintended commands, kernel versions with known local exploits, and cron jobs pointing at scripts you can write to. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Red Team Tactics
Red teaming exists to make defenders better by safely rehearsing how a real attacker would behave. Everything below assumes written authorization, a defined scope, and an intent to report rather than to harm.
The ATT&CK lifecycle
An engagement moves through recognizable stages. They are not strictly linear -- escalation and discovery often loop -- but each has a job:
| Stage | What it accomplishes |
|---|---|
| Reconnaissance | chart the attack surface |
| Initial access | establish the first foothold |
| Execution | run code on the target |
| Persistence | survive reboots and logouts |
| Privilege escalation | reach admin or root |
| Defense evasion | stay below detection thresholds |
| Credential access | collect usable credentials |
| Discovery | learn the internal layout |
| Lateral movement | reach additional hosts |
| Collection | gather the data of interest |
| Command & control | hold a reliable channel back |
| Exfiltration / impact | remove data or demonstrate effect |
Reconnaissance
The first trade-off is passive versus active. Passive collection never touches the target -- low risk, limited yield. Active probing engages it directly -- richer data, higher chance of being noticed. Sequence accordingly: exhaust passive sources before generating traffic.
What is worth finding, and why:
| Finding | Why it matters |
|---|---|
| Technology stack | shapes which exploits are viable |
| Staff and roles | feeds social-engineering pretexts |
| IP/network ranges | bounds the scanning scope |
| Vendors and partners | opens supply-chain angles |
Gaining initial access
Choose the vector that fits the target and the rules of engagement:
| Vector | When it fits |
|---|---|
| Phishing | a human target with reachable email |
| Public exploit | an exposed, unpatched service |
| Valid credentials | leaked, reused, or cracked logins |
| Supply chain | trusted third-party access exists |
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.
- 1mo ago First seen · 113 lines · 89 tokens per session scan A 8bf0be603d39
red-team-tactics is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 3mo ago), licensed MIT. It adds 89 tokens to every session and 1,086 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
memory-retain
Save what was learned to Hindsight long-term memory. Use when a task finishes, when the user states a fact, decision or preference, and when you discover something a later run or another Bot would need.
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
web-platform-baseline
Use this skill before asserting that a CSS, HTML or accessibility capability is available, unavailable, or the right tool — it carries dated, refreshable platform facts and refuses to let stale knowledge be stated as current. Triggers: user says "container query", "can I use", "browser support", "modern CSS", ":has"…
doc-coauthoring
Collaboratively author technical specifications, RFCs, PRDs, ADRs, and decision documents through structured context gathering, iterative refinement, and blind reader testing. Use when drafting substantial documentation, architecture proposals, or engineering design records.