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 FFmorange/QDeskWatch --skill project-file-searchgit clone --depth 1 https://github.com/FFmorange/QDeskWatchWrote 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/ffmorange/qdeskwatch/project-file-search)<a href="https://agentmods.dev/skills/ffmorange/qdeskwatch/project-file-search"><img src="https://agentmods.dev/badge/skills/ffmorange/qdeskwatch/project-file-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/ffmorange/qdeskwatch/project-file-search"><img src="https://agentmods.dev/badge/skills/ffmorange/qdeskwatch/project-file-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.00062 | $0.00401 |
| Opus 5 | $0.00031 | $0.00200 |
| Sonnet 5 | $0.00012 | $0.00080 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
project-file-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 9d 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
项目文件检索
先读结构文档，再精准定位当前项目中的文件与模块。
工作流程
- 先读取
docs/project-file-structure.md。 - 先判断当前需求最接近仓库中的哪一块区域。
- 使用
rg --files或rg缩小候选文件范围。 - 只打开最相关的文件，并确认真正的改动落点。
- 输出具体路径，并为每个关键路径补一条简短原因。
检索规则
- 把
docs/project-file-structure.md视为仓库地图，在进行大范围搜索前先读它。 - 文件发现优先用
rg --files，文本检索优先用rg。 - 将
.qtcreator/视为 IDE 本地配置，将build/视为编译产物；除非用户明确要求，否则不要深入检查。 - 将
install/与plugins/market/优先视为生成物或分发落点，而不是主源码真值来源。 - 如果结构文档与仓库当前状态不一致，以当前仓库实际文件为准，并指出文档可能需要同步更新。
输出要求
- 返回独立、明确的文件路径，不只给目录级猜测。
- 如果有多个相关路径，先指出主要改动落点，再列补充路径。
- 如果请求同时跨越 QML、C++ 和插件边界，在开始编辑前要明确说出来。
What ships with it
1 file 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.
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.
- 9d ago First seen · 31 lines · 62 tokens per session scan A e60e64780bc7
project-file-search is a skill published in the GitHub repository FFmorange/QDeskWatch (2 stars, last pushed 4mo ago), licensed MIT. It adds 62 tokens to every session and 401 once invoked, about $0.0003 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.