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 instructions/whulxc/remocli/agents-mdgit clone --depth 1 https://github.com/whulxc/remocliWrote 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/instructions/whulxc/remocli/agents-md)<a href="https://agentmods.dev/instructions/whulxc/remocli/agents-md"><img src="https://agentmods.dev/badge/instructions/whulxc/remocli/agents-md.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.00997 | $0.00997 |
| Opus 5 | $0.00498 | $0.00498 |
| Sonnet 5 | $0.00199 | $0.00199 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
remocli AGENTS.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl -sS http://127.0.0.1:8080/health` How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RemoCLI Maintenance Guide
This repository is maintained as a Windows + WSL control plane for remote CLI sessions. Use this file as the default engineering context for new maintenance sessions.
What matters first
- Treat the stack as four layers:
gateway- per-WSL
agent - transport (
USB,LAN,Quick tunnel preview,Formal public deployment) - Android/Web client state
- For connection or login problems, always check layers in that order.
- Do not start from app-side guessing when
gatewayoragenthealth is unknown.
Primary entrypoints
- Gateway server:
src/gateway/server.js - Agent server:
src/agent/server.js - Frontend app:
src/frontend/app.js - Android shell:
android/app/src/main/java/com/remoteconnect/mobile/MainActivity.kt - Deployment config generation:
scripts/generate-deployment-config.mjs - Public deployment notes:
docs/public-deployment-modes.md - Troubleshooting:
docs/troubleshooting.md
Default troubleshooting flow
1. Identify the active mode
USB directLAN directQuick tunnel previewFormal public deployment
Do not treat the Cloudflare Access team domain as the application hostname.
2. Check the local stack
- Gateway:
curl -sS http://127.0.0.1:8080/health
- Agent:
node scripts/check-deployment.mjs <deployment-manifest>
- Logs:
tail -n 80 data/runtime/gateway.logtail -n 80 data/runtime/agent-*.log
3. Check the transport
- USB:
adb devicesadb reverse --list
- LAN:
- test the Windows LAN URL from the host first
- Formal public:
curl -I https://<public-hostname>- if
1033, check named tunnel state and logs
4. Only then check client state
- Web page stale state: refresh once
- Android stale state: reopen app once
- Only use UI tree /
logcatwhen:- the user says “still broken”, or
- server-side state is healthy but phone behavior disagrees
Low-token maintenance defaults
- Do not restate the entire README in every maintenance session.
- Read
AGENTS.mdfirst, then only open files relevant to the active problem. - Prefer short status reports:
- root cause
- exact fix
- validation
- whether web refresh / app reopen / gateway restart / agent restart is needed
- For repeat issues, reuse the same path:
- mode -> gateway -> agent -> transport -> client
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 · 134 lines · 997 tokens per session scan A f30693d4f86d
remocli AGENTS.md is an instructions file published in the GitHub repository whulxc/remocli (5 stars, last pushed 5mo ago), licensed MIT. It adds 997 tokens to every session, about $0.0050 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
dsh-mobile-apk AGENTS.md
AGENTS.md instructions for kelai141/dsh-mobile-apk, covering agents.md — dsh-mobile-apk 开发地图, 1. 仓库概览与技术栈, 2. 构建与验证命令, 一键双 abi（协调仓库根；快照→注入→门禁→gradle→out/）： and 快照（termux 源 + targets 预装 + licenses + pnpm 装配 + 瘦身 + 归档）：.
webspace_app CLAUDE.md
Claude Code instructions for theoden8/webspace_app, covering claude.md, style (output, code, commits), git, sandbox bootstrap and fvm — required (.fvmrc pins flutter 3.38.6).
j3w1zsh AGENTS.md
AGENTS.md instructions for j3w1/j3w1zsh, covering j3w1zsh agent instructions, purpose and authority, start every run, security and privacy and platform and installer contract.
agentcrew-dev-skills AGENTS.md
AGENTS.md instructions for okqixiaobao727-design/agentcrew-dev-skills, covering agents.md and validating your work.
vps-agent AGENTS.md
AGENTS.md instructions for meoyawn/vps-agent, covering agents.md, project vocab/refs and rules.
review-switch AGENTS.md
AGENTS.md instructions for okqixiaobao727-design/review-switch, covering review-switch, agent skills, issue tracker, triage labels and domain docs.