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 tristanmanchester/sifs --skill sifs-searchgit clone --depth 1 https://github.com/tristanmanchester/sifsWrote 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/tristanmanchester/sifs/sifs-search)<a href="https://agentmods.dev/skills/tristanmanchester/sifs/sifs-search"><img src="https://agentmods.dev/badge/skills/tristanmanchester/sifs/sifs-search/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/tristanmanchester/sifs/sifs-search"><img src="https://agentmods.dev/badge/skills/tristanmanchester/sifs/sifs-search.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.00094 | $0.00584 |
| Opus 5 | $0.00047 | $0.00292 |
| Sonnet 5 | $0.00019 | $0.00117 |
| Haiku 4.5 | $0.00009 | $0.00058 |
Grade A, and why
sifs-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 12d 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
Use SIFS from the shell when you need codebase context. The CLI is the reliable path; MCP tools are optional and should only be used when they are visible in the current agent session.
When to Use
- Use for local code search, symbol discovery, behavior tracing, related-code lookup, and indexed file/chunk inspection.
- Use before reading many files by hand when the task starts with "where is...", "how is...", "find the implementation...", or "what code handles...".
- Do not use for general web research, package documentation lookup, or non-code document search unless the user explicitly points SIFS at a source tree.
Start by discovering the local contract:
sifs agent-context --json
Search by intent, behavior, symbol, or exact text:
sifs search "authentication flow" --source <project>
sifs search "save_pretrained" --source <project> --mode bm25
sifs search "save model to disk" --source <project> --limit 10
Inspect indexed files and chunks before reading broad files:
sifs list-files --source <project> --limit 200 --json
sifs list-files --source <project> --prefix src/auth/ --json
sifs symbol SessionToken --source <project> --json
sifs outline src/auth.rs --source <project> --symbols-limit 200 --chunks-limit 100 --json
sifs get src/auth.rs 42 --source <project>
sifs find-related src/auth.rs 42 --source <project>
Use --source <project> when the agent may not be running from the target checkout. Use --filter-path <repo-relative-path> for path narrowing and --limit for bounded results.
If MCP tools named search, symbol, outline, pack, get_chunk, or list_files are visible, they may be used for the same workflow. If they are missing, configured-but-invisible, or failing, fall back to the CLI immediately.
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.
- 12d ago First seen · 47 lines · 94 tokens per session scan A 61ec982d87af
sifs-search is a skill published in the GitHub repository tristanmanchester/sifs (2 stars, last pushed 3mo ago), licensed MIT. It adds 94 tokens to every session and 584 once invoked, about $0.0005 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.