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 meltedinhex/analyst-ai-pack --skill hunting-scheduled-task-abusegit clone --depth 1 https://github.com/meltedinhex/analyst-ai-packWrote 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/meltedinhex/analyst-ai-pack/hunting-scheduled-task-abuse)<a href="https://agentmods.dev/skills/meltedinhex/analyst-ai-pack/hunting-scheduled-task-abuse"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/hunting-scheduled-task-abuse/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/meltedinhex/analyst-ai-pack/hunting-scheduled-task-abuse"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/hunting-scheduled-task-abuse.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.00063 | $0.00691 |
| Opus 5 | $0.00032 | $0.00345 |
| Sonnet 5 | $0.00013 | $0.00138 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
hunting-scheduled-task-abuse 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.
What it actually says
Hunting Scheduled Task Abuse
When to Use
- You have task-registration events (4698) and/or
schtasks.exe/at.exeprocess telemetry and want to detect persistence via malicious scheduled tasks. - You are investigating tasks that run scripts, encoded commands, or binaries from suspicious paths.
Do not use this to alert on all task creation — administration creates tasks routinely. Hunt on the action (script hosts, encoded commands, temp paths) and trigger context.
Prerequisites
- Event ID 4698 (task registered) and/or process-creation telemetry for
schtasks/at.
Workflow
Step 1: Hunt suspicious task actions
python scripts/analyst.py hunt events.csv
Flags tasks whose action runs powershell -enc, mshta, wscript/cscript, cmd /c, or
binaries from %TEMP%/%APPDATA%/Public, and schtasks /create command lines with the same.
Step 2: Assess triggers and hiding
Note logon/onstart triggers, very frequent intervals, and tasks hidden via Hidden flag or SD
manipulation.
Step 3: Confirm
Distinguish legitimate software tasks from intrusion by author, path, and action content.
Step 4: Operationalize
Write a Sigma rule for task actions invoking script hosts or encoded commands.
Validation
- Flags require a suspicious action/path, not task creation alone.
schtasks /createand 4698 registrations are both covered.- Findings map to ATT&CK T1053.005.
Pitfalls
- Legitimate updater tasks (browsers, vendors) creating many tasks.
- Tasks created via direct XML drop bypassing
schtasks.exetelemetry. - Encoded commands hiding the true action.
References
- See
references/api-reference.mdfor the hunter. - ATT&CK T1053.005 and Event 4698 docs (linked in frontmatter).
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 87 lines · 63 tokens per session scan A 3c5caf5a86e1
hunting-scheduled-task-abuse is a skill published in the GitHub repository meltedinhex/analyst-ai-pack (22 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 691 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
hunting-for-registry-run-key-persistence
Use when detect MITRE ATT&CK T1547.001 registry Run key persistence by analyzing Sysmon Event ID 13 logs and registry queries to identify malicious auto-start entries. Use when detecting mitre att&ck t1547.001 registry run key persistence by analyzing.
analyzing-cobalt-strike-beacon-configuration
Extract and analyze Cobalt Strike beacon configuration from PE files and memory dumps to identify C2 infrastructure, malleable profiles, and operator tradecraft.
analyzing-golang-malware-with-ghidra
Reverse engineer Go-compiled malware in Ghidra by parsing Go buildinfo and pclntab structures, recovering stripped/obfuscated function names (e.g. via GoResolver), and extracting embedded module/dependency strings and types from Go binaries. Use when analyzing a Go-language malware sample, deobfuscating a…
analyzing-malware-persistence-with-autoruns
Use Sysinternals Autoruns to systematically enumerate and analyze malware persistence mechanisms across Windows registry run keys, scheduled tasks, services, drivers, and startup locations. Use when hunting for persistence during Windows incident response, triaging a compromised endpoint, or validating that malware…
analyzing-malicious-pdf-with-peepdf
Perform static analysis of malicious PDF documents using peepdf, pdfid, and pdf-parser to extract embedded JavaScript, shellcode, and suspicious objects. Use when triaging a suspicious PDF attachment from a phishing email, analyzing a PDF-based exploit document, or building detection signatures for weaponized PDF…
detecting-email-forwarding-rules-attack
Detect malicious email forwarding rules created by adversaries to maintain persistent access to email communications for intelligence collection and BEC attacks.