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 agentmods add skills/0dayinc/pwn/task_summarizernpx skills add 0dayInc/pwn --skill task_summarizergit clone --depth 1 https://github.com/0dayInc/pwnWrote 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/0dayinc/pwn/task_summarizer)<a href="https://agentmods.dev/skills/0dayinc/pwn/task_summarizer"><img src="https://agentmods.dev/badge/skills/0dayinc/pwn/task_summarizer.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 | $0.00026 | $0.00702 |
| Opus 5 | $0.00013 | $0.00351 |
| Sonnet 5 | $0.00005 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
pwn-ai-agent-tasksummarizer 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PWN::AI::Agent::TaskSummarizer
High-level executive brief of the work the agent is about to do. Every pwn-ai request is a goal. There is no statement/question/goal request type. English tangible tasks are an advisory compass: 1. plan(request:) — break the goal into ordered plain-English tasks 2. about_to(tools:) — per tool-batch brief led by "task k/n" 3. active_task_prompt — injected into Loop as a compass only 4. record! emits an advancement brief when plan_idx moves Never dumps raw commands or tool results into the task row — those stay on the per-tool lines the REPL already prints. REPL on_tool contract (repl.rb): on_tool.call('task', full_summary_text, '') # result MUST be empty # → [ ts → pwn-ai → task ] <full summary, no truncation> on_tool.call('shell', args, result) # real tool
When to use
Call PWN::AI::Agent::TaskSummarizer from pwn_eval when the task needs this module.
Do not reimplement it in shell.
Methodologies
Generated from pwn/ai/agent/task_summarizer.rb. Prefer the public class methods below.
Class methods take (opts = {}) and read opts.
How to call
PWN::AI::Agent::TaskSummarizer.help
PWN::AI::Agent::TaskSummarizer.enabled(opts)
Public methods
enabledverbosellm_plan_enabledevery_ninterval_sfreshneeds_task_breakdownplanformat_planemit_planchat_for_planparse_llm_tasksfallback_decomposeheuristic_decomposeabout_toactive_taskunfinished_tasksplan_openplan_contextrelevance_queryactive_task_promptcanonical_requesttool_jargon_taskparse_outline_tasksunify_planapply_prm_advancementrecordemitflushauthorshelpapply_prm_advancement!emit!emit_plan!enabled?flush!llm_plan_enabled?needs_task_breakdown?plan_open?record!tool_jargon_task?unify_plan!verbose?
Source
pwn/ai/agent/task_summarizer.rb
Verification
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.
- 4d ago First seen · 88 lines · 26 tokens per session scan A 9fb4070b5ea1
pwn-ai-agent-tasksummarizer is a skill published in the GitHub repository 0dayInc/pwn (78 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 702 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
analyzing-linux-elf-malware
Analyze malicious Linux ELF binaries — botnets, cryptominers, ransomware, and rootkits targeting Linux servers, containers, and cloud infrastructure — through static analysis, dynamic tracing, and reverse engineering of x8664 and ARM samples. Use when investigating Linux malware, triaging a suspicious ELF binary…
osmedeus-expert
Expert guide for the Osmedeus security automation workflow engine. Use when: (1) writing or editing YAML workflows (modules and flows), (2) running osmedeus CLI commands (scan, workflow management, installation, server), (3) configuring steps, runners, triggers, or template variables, (4) debugging workflow execution…
performing-jwt-none-algorithm-attack
Execute and test the JWT none algorithm attack to bypass signature verification by manipulating the alg header field in JSON Web Tokens.
performing-ai-assisted-vulnerability-discovery
Using LLMs to accelerate vulnerability research and pentest workflows — generating syntax-valid fuzzing seeds and evolving grammars, fine-tuned mutation dictionaries, parallel agent-based proof-of-vulnerability generation, and evidence-driven passive analysis of real HTTP traffic via the Burp MCP server. Covers…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
graphql
GraphQL pentest playbook — find the endpoint, dump the schema (introspection or field-suggestion fallback), then test for authorization gaps, query batching, alias overload, depth-based DoS, and SQLi/NoSQLi in resolver arguments. Use when the target exposes a /graphql endpoint, GraphiQL, Apollo, or accepts GraphQL…