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.
git clone --depth 1 https://github.com/ImL1s/GUI-AnythingWrote 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/iml1s/gui-anything/list)<a href="https://agentmods.dev/commands/iml1s/gui-anything/list"><img src="https://agentmods.dev/badge/commands/iml1s/gui-anything/list/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/commands/iml1s/gui-anything/list"><img src="https://agentmods.dev/badge/commands/iml1s/gui-anything/list.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.00000 | $0.00163 |
| Opus 5.5 | $0.00000 | $0.00065 |
| Sonnet 5.5 | $0.00000 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
list 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 1mo 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
/gui-anything:list — List Existing Harnesses
List all GUI-Anything harnesses in the current repository.
Usage
/gui-anything:list
Procedure
- Scan all top-level directories for
agent-harness/subdirectories - For each harness found, read
gui-schema.jsonandagent-harness/mcp-tools.json - Display summary table:
Software | Actions | MCP Tools | Status
-------------|---------|-----------|--------
calculator | 12 | 15 | ✓ valid
- If no harnesses found, suggest using
/gui-anything <path>to create one
Output Format
- Markdown table for human readability
- JSON array for
--jsonmode
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.
- 1mo ago First seen · 29 lines · 0 tokens per session scan A e9337f8b6654
list is a command published in the GitHub repository ImL1s/GUI-Anything (5 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 163 tokens. 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
retro-learn
Convert delivery findings into skill, eval, workflow, and documentation improvements.
sync
Manually trigger plan-sync to update downstream task specs after implementation drift.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
me-figure-discussion
Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.
sounds
List available notification sounds and preview them.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.