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/imoonkey/openweb/angellistnpx skills add imoonkey/openweb --skill angellistgit clone --depth 1 https://github.com/imoonkey/openwebWrote 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/imoonkey/openweb/angellist)<a href="https://agentmods.dev/skills/imoonkey/openweb/angellist"><img src="https://agentmods.dev/badge/skills/imoonkey/openweb/angellist.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.00000 | $0.00539 |
| Opus 5 | $0.00000 | $0.00269 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
angellist 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AngelList Venture
Overview
AngelList Venture (venture.angellist.com) — investor-side dashboard for syndicates, deals, and LP messaging. Logged-in only. Read-only coverage.
Workflows
Review pending deal invites
listInvites→ all current invites with deal id, name, syndicate, statusgetInvite(virtualDealId)→ data room: memo, deck, slides, attachments (via portal.angellist.com)
Read inbox messages
listMessages→ paginated message threads with participants, last message, unread statusgetMessage(conversationId)→ full thread with all messages
Read syndicate posts
listPosts→ paginated syndicate posts with title, author, dategetPost(postId)→ full post body, syndicate, documents
Operations
| Operation | Intent | Key Input | Key Output | Transport |
|---|---|---|---|---|
| listInvites | current deal pipeline | — | id, dealName, virtualDealId, syndicateName, canInvest, investUrl | adapter (page, Apollo) |
| getInvite | deal data room | virtualDealId ← listInvites | senderOrgHandle, sections[].header, sections[].content, sections[].files[] | adapter (page, intercept portal) |
| listMessages | inbox threads | limit?, cursor? | conversations[].id, participants, lastMessage, isUnread | adapter (page, Apollo) |
| getMessage | thread messages | conversationId ← listMessages | participants, messages[].text, messages[].sentAt, messages[].sentBy | adapter (page, Apollo) |
| listPosts | syndicate posts | limit?, cursor? | posts[].id, title, fromName, publishAt, isUnread | adapter (page, Apollo) |
| getPost | full post | postId ← listPosts | title, body, fromName, syndicateName, documents | adapter (page, Apollo) |
Known Limitations
- Logged-in only; session cookies from default Chrome profile.
getInvitenavigates to portal.angellist.com (cross-origin); fund-type and deal-type invites may have different data room layouts.x-al-gqlsigning header requires Apollo client.query() via main-world CDP — patchright's isolated evaluate cannot access__APOLLO_CLIENT__.- GraphQL
messagesresolver requiresconversationIdpassed directly to themessages()field, not just the parentconversation().
What ships with it
11 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.
- adapters/angellist.ts 12 KB runs code
- DOC.md 2.2 KB
- examples/getInvite.example.json 233 B
- examples/getMessage.example.json 236 B
- examples/getPost.example.json 224 B
- examples/listInvites.example.json 195 B
- examples/listMessages.example.json 222 B
- examples/listPosts.example.json 219 B
- manifest.json 339 B
- openapi.yaml 12 KB
- PROGRESS.md 4.1 KB
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 · 36 lines · 0 tokens per session scan A 078f90464142
angellist is a skill published in the GitHub repository imoonkey/openweb (60 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 539 tokens. 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
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…