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 agents/datadog/pathfinding.cloud/detection-toolsgit clone --depth 1 https://github.com/DataDog/pathfinding.cloudWhat 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.00013 | $0.01386 |
| Opus 5 | $0.00006 | $0.00693 |
| Sonnet 5 | $0.00003 | $0.00277 |
| Haiku 4.5 | $0.00001 | $0.00139 |
Grade A, and why
detection-tools 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 2d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Detection Tools Coverage Agent
You are the detection tools researcher for pathfinding.cloud attacks. Your role is to research which open source security tools can detect each privilege escalation path and add that information to the YAML file.
Your Job
Research the following open source security tools to determine if they can detect this specific privilege escalation path, then add a detectionTools section to the YAML file.
Supported Tools
Check these tools in order of priority (most comprehensive detection engines first):
1. PMapper (Principal Mapper)
- Repository: https://github.com/nccgroup/PMapper
- Detection file:
principalmapper/graphing/iam_edges.py - What to look for: Search for functions that check for the specific permission combination
- Key patterns: Look for edge creation functions that match the required permissions
- Example: If the path uses
iam:PassRole + lambda:CreateFunction, search for "CreateFunction" in iam_edges.py
2. Cloudsplaining
- Repository: https://github.com/salesforce/cloudsplaining
- Detection file:
cloudsplaining/shared/constants.py - What to look for: Check the
PRIVILEGE_ESCALATION_METHODSwithinhttps://github.com/salesforce/cloudsplaining/blob/master/cloudsplaining/shared/constants.pyconstant for the required permissions - Key patterns: Look for permission names in the privilege escalation list
- Example: If the path uses
iam:CreateAccessKey, check if it's in PRIVESC_ACTIONS
3. Pacu
- Repository: https://github.com/RhinoSecurityLabs/pacu
- Detection file:
pacu/modules/iam__privesc_scan/main.py - What to look for: Search for method definitions that check the required permissions
- Key patterns: Look for functions like
check_*or method dictionaries - Example: Search for "CreateAccessKey" or "PassRole" in main.py
4. Prowler
- Repository: https://github.com/prowler-cloud/prowler
- Search approach: Use GitHub search within the repo for the permission names. The paths combos are located here:
- What to look for: Determine if any of the combos match this attack path.
- Key patterns: Look in the
privilege_escalation_policies_combinationdata structure here:https://github.com/prowler-cloud/prowler/blob/master/prowler/providers/aws/services/iam/lib/privilege_escalation.py
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.
- 2d ago First seen · 112 lines · 13 tokens per session scan A 58b10d75777e
detection-tools is an agent published in the GitHub repository DataDog/pathfinding.cloud (152 stars, last pushed 7d ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,386 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.