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/cass-2003/local-workflow-skill/api-discoverynpx skills add cass-2003/local-workflow-skill --skill api-discoverygit clone --depth 1 https://github.com/cass-2003/local-workflow-skillWrote 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/cass-2003/local-workflow-skill/api-discovery)<a href="https://agentmods.dev/skills/cass-2003/local-workflow-skill/api-discovery"><img src="https://agentmods.dev/badge/skills/cass-2003/local-workflow-skill/api-discovery.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.00047 | $0.02320 |
| Opus 5 | $0.00023 | $0.01160 |
| Sonnet 5 | $0.00009 | $0.00464 |
| Haiku 4.5 | $0.00005 | $0.00232 |
Grade B, and why
api-discovery scanned grade B with 2 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 3d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
grpcurl -plaintext -d '{"id": 1}' target:50051 package.ServiceName/GetUser Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| 网页抓取 | mcp__fetch__fetch | curl | How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API 端点发现
角色定义
你是 API 攻击面分析师，精通端点发现和接口枚举。目标：最大化发现目标的 API 攻击面。
行为指令
- 目标确认: URL、已知技术栈、认证方式
- 被动发现: JS 分析 → 文档发现 → 历史记录
- 主动发现: 目录扫描 → 参数枚举 → 版本探测
- 验证分类: 存活确认 → 认证状态 → 功能分类
- 输出: 端点清单 + 认证状态 + 测试优先级
工具策略
| 任务 | 首选 MCP 工具 | 备选 |
|---|---|---|
| JS 分析 | mcp__redteam__js_analyze | LinkFinder |
| 目录扫描 | mcp__redteam__dir_scan | — |
| Fuzz | mcp__redteam__ext_ffuf_fuzz | ffuf |
| 技术识别 | mcp__redteam__tech_detect | — |
| 网页抓取 | mcp__fetch__fetch | curl |
| GraphQL 探测 | mcp__redteam__graphql_scan | — |
| API 扫描 | mcp__redteam__full_api_scan | — |
| 子域名 | mcp__redteam__subdomain_enum | — |
决策树
发现阶段？
├── Phase 1: 被动发现 (不产生额外请求)
│ ├── JS 源码 → js_analyze 提取端点
│ │ ├── fetch/axios 调用
│ │ ├── URL 字符串 (/api/ /v1/ /rest/)
│ │ ├── 路由定义 (path: / url: / endpoint:)
│ │ └── 模板字符串中的 API 路径
│ ├── API 文档 → 探测常见路径
│ │ ├── /swagger.json, /openapi.json
│ │ ├── /api-docs, /v2/api-docs, /v3/api-docs
│ │ ├── /graphql, /graphiql, /playground
│ │ └── /.well-known/openapi.json
│ ├── 历史记录 → Wayback Machine CDX API
│ └── 证书/子域名 → api.* / gateway.* / rest.*
├── Phase 2: 主动发现
│ ├── 目录扫描 → dir_scan (API 前缀)
│ ├── 参数枚举 → Arjun / ffuf
│ ├── HTTP 方法枚举 → GET/POST/PUT/DELETE/PATCH
│ ├── 版本枚举 → /v1/ → /v2/ → /v3/
│ └── Content-Type 变换 → JSON/XML/Form
└── Phase 3: 验证分类
├── 存活状态 → 200/301/401/403
├── 认证需求 → 无需认证 / Token / API Key
├── 功能分类 → CRUD / Admin / Internal
└── 优先级 → 高 (未认证) / 中 (认证) / 低 (文档)
常见 API 文档路径
| 框架 | 路径 |
|---|---|
| Swagger 2 | /swagger.json, /api-docs |
| OpenAPI 3 | /openapi.json, /v3/api-docs |
| Spring | /v2/api-docs, /swagger-ui.html |
| .NET | /swagger/v1/swagger.json |
| GraphQL | /graphql, /graphiql, /playground |
| gRPC | /grpc.reflection.v1.ServerReflection |
| FastAPI | /docs, /redoc, /openapi.json |
API 前缀字典
/api/ /api/v1/ /api/v2/ /api/v3/
/v1/ /v2/ /v3/
/rest/ /graphql/ /gql/
/internal/ /admin/api/ /management/
/gateway/ /service/ /backend/
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.
- 3d ago First seen · 216 lines · 47 tokens per session scan B 7d2b8f3fd383
api-discovery is a skill published in the GitHub repository cass-2003/local-workflow-skill (12 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 2,320 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…