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 commands/razaib-khan/forgeweave/forge-searchgit clone --depth 1 https://github.com/Razaib-khan/ForgeWeaveWrote 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/commands/razaib-khan/forgeweave/forge-search)<a href="https://agentmods.dev/commands/razaib-khan/forgeweave/forge-search"><img src="https://agentmods.dev/badge/commands/razaib-khan/forgeweave/forge-search.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.1 | $0.00016 | $0.00343 |
| Opus 5 | $0.00008 | $0.00171 |
| Sonnet 5 | $0.00003 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
forge-search 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 5d 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
Forge Search
Triggers the websearch tool for lightweight on-demand web searches. Use this when you need a quick answer about an API, error, library, or configuration detail — not a full research pipeline.
Usage: /forge-search <query> [--max=<1-10>] [--source=<domain.com>]
When to Use
- You don't know a specific API parameter, function signature, or import path
- You encounter an error message you haven't seen before
- You need a quick code example for a specific method
- You need to confirm a library version, feature flag, or deprecation
- You need to verify a CLI flag or configuration option
- You are about to write code with an unfamiliar library — stop and search first
When NOT to Use
- The question requires comparing 3+ sources or understanding a new framework — use
/forge-research - The information is in the local codebase — search the codebase directly
- The user asked for a comprehensive report — use
/forge-research
Behavior
- Calls
websearchwith the query and options - Returns top results with extracted content from each source
- Results are synchronous — no polling needed
Examples
/forge-search next.js 16 cacheLife default profile
/forge-search python 3.14 match statement syntax
/forge-search playwright mcp browser_snapshot --source=playwright.dev
/forge-search react 19 useActionState signature --max=3
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.
- 5d ago First seen · 41 lines · 16 tokens per session scan A a823acca0f60
forge-search is a command published in the GitHub repository Razaib-khan/ForgeWeave (1 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 343 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-31.
Other commands, from other repositories
agentlas-cloud
Staff a task only from the signed-in owner's Agent Cloud agents.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
dashboard-session-diff
Show file changes (git diff) for a session by id-prefix. Usage /dashboard:session-diff . Runs locally, no LLM.
dashboard-session-list
List all pi sessions (id, status, name, cwd). Runs locally, no LLM.
os-meeting
快速创建和管理AI团队会议.
spec-intake
Execute the canonical workflow: .agent/workflows/spec-intake.md.