Borrowing it
Nothing to install: this file belongs to HE1780/deer-flow-by-cc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/HE1780/deer-flow-by-cc/main/.agent/skills/smoke-test/SKILL.mdgit clone --depth 1 https://github.com/HE1780/deer-flow-by-ccWrote 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/he1780/deer-flow-by-cc/smoke-test)<a href="https://agentmods.dev/skills/he1780/deer-flow-by-cc/smoke-test"><img src="https://agentmods.dev/badge/skills/he1780/deer-flow-by-cc/smoke-test/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/he1780/deer-flow-by-cc/smoke-test"><img src="https://agentmods.dev/badge/skills/he1780/deer-flow-by-cc/smoke-test.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.00100 | $0.02108 |
| Opus 5 | $0.00050 | $0.01054 |
| Sonnet 5 | $0.00020 | $0.00422 |
| Haiku 4.5 | $0.00010 | $0.00211 |
Grade A, and why
smoke-test 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 10d 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.
This is a copy
84% identical to smoke-test — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DeerFlow Smoke Test Skill
This skill guides the Agent through DeerFlow's full end-to-end smoke test workflow, including code updates, deployment (supporting both Docker and local installation modes), service availability verification, and health checks.
Deployment Mode Selection
This skill supports two deployment modes:
- Local installation mode (recommended, especially when network issues occur) - Run all services directly on the local machine
- Docker mode - Run all services inside Docker containers
Selection strategy:
- If the user explicitly asks for Docker mode, use Docker
- If network issues occur (such as slow image pulls), automatically switch to local mode
- Default to local mode whenever possible
Structure
smoke-test/
├── SKILL.md ← You are here - core workflow and logic
├── scripts/
│ ├── check_docker.sh ← Check the Docker environment
│ ├── check_local_env.sh ← Check local environment dependencies
│ ├── frontend_check.sh ← Frontend page smoke check
│ ├── pull_code.sh ← Pull the latest code
│ ├── deploy_docker.sh ← Docker deployment
│ ├── deploy_local.sh ← Local deployment
│ └── health_check.sh ← Service health check
├── references/
│ ├── SOP.md ← Standard operating procedure
│ └── troubleshooting.md ← Troubleshooting guide
└── templates/
├── report.local.template.md ← Local mode smoke test report template
└── report.docker.template.md ← Docker mode smoke test report template
Standard Operating Procedure (SOP)
Phase 1: Code Update Check
- Confirm current directory - Verify that the current working directory is the DeerFlow project root
- Check Git status - See whether there are uncommitted changes
- Pull the latest code - Use
git pull origin mainto get the latest updates - Confirm code update - Verify that the latest code was pulled successfully
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.
- references/SOP.md 9.6 KB
- references/troubleshooting.md 11 KB
- scripts/check_docker.sh 2.0 KB runs code
- scripts/check_local_env.sh 2.4 KB runs code
- scripts/deploy_docker.sh 1.7 KB runs code
- scripts/deploy_local.sh 1.5 KB runs code
- scripts/frontend_check.sh 2.0 KB runs code
- scripts/health_check.sh 3.0 KB runs code
- scripts/pull_code.sh 1.2 KB runs code
- templates/report.docker.template.md 4.5 KB
- templates/report.local.template.md 4.6 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.
- 10d ago First seen · 182 lines · 0 tokens per session scan A e181f04c91a1
smoke-test is a skill published in the GitHub repository HE1780/deer-flow-by-cc (23 stars, last pushed 4mo ago), licensed MIT. It adds 100 tokens to every session and 2,108 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to smoke-test, differing in 21 lines, and is treated as a copy.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…