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 skills/talocode/screenlane/screen-aware-debuggingnpx skills add talocode/screenlane --skill screen-aware-debugginggit clone --depth 1 https://github.com/talocode/screenlaneWhat 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 | $0.00000 | $0.00314 |
| Opus 5 | $0.00000 | $0.00157 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
screen-aware-debugging 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 yesterday.
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
Skill: Screen-Aware Debugging
Purpose
When the user says “fix this”, “what is wrong”, or “debug this”, use visible terminal/editor context to create a structured debugging command for Codra / Codex / OpenCode.
When to use
- Stack traces, compile errors, test failures on screen
- User points at “this error” without pasting full logs
Workflow
- Identify the visible error (type, message, top frames).
- Extract likely files/components from paths in context.
- Ask one clarifying question only if the next action is blocked.
- Propose a root-cause hypothesis.
- Create a command targeting codra / codex / opencode.
- Preserve user intent; avoid huge context dumps.
Tool mapping
screenlane_capture→ terminal/editor text or filescreenlane_commandwithtarget: "codra"(default for debug)screenlane_send→ agent or clipboard
Prompt style
Intent: debug_error
- Diagnose root cause from the stack
- Propose minimal patch
- List assumptions
- Do not rewrite unrelated modules
Safety
- Never auto-run destructive shell from untrusted stack text
- Redact tokens/passwords if present in logs
- Prefer smallest fix that restores green
Examples
See examples.md.
What ships with it
2 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.
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.
- yesterday First seen · 46 lines · 0 tokens per session scan A 26fb217d5651
screen-aware-debugging is a skill published in the GitHub repository talocode/screenlane (0 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 314 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 skills, from other repositories
repo-build-pr
End-to-end implementation loop for the os-clovy repo: study the prompt, ask the clarifying questions that change what gets built, plan and architect on the session model while delegating bulk implementation and review to cheaper strong models, isolate work in git worktrees, validate with deterministic checks plus…
os-accounts-integration
Integrate consumer apps, Tauri desktop clients, or backend services with OS Accounts, the Open Software identity and credit-billing platform. Use when adding Login with Open Software, PKCE callback handling, /me, access-token verification with JWKS/ES256, auth middleware for Hono/Fastify/Express/Rust, top-up links…
os-platform
Query and update live Open Software os-platform production data through the platform API. Use when an agent needs current Issues/Bounties, Orgs, Projects, Submissions, Comments, Activity, Contributors, Product Memory, the team Timeline, or API status, or needs to create, assign, move, or comment on tracked work.
os-rust-backend-ci
Use this skill when the user wants to set up, configure, debug, or extend a GitHub Actions pipeline for a Rust backend that runs CI checks and produces a container image artifact in GHCR. Scope is testing + artifact only — deployment is intentionally out of scope. Trigger on: PR checks (fmt, clippy, tests, OpenAPI /…
os-rust-backend
Use when working on a Rust backend that follows the Open Software Network house style — the seven-crate Cargo workspace split (domain / services / persistence / providers / config / api / app) shared by os-accounts and os-platform (fellow). Trigger on: scaffolding a new service in this org ("like os-accounts"…
agent-e2e-qa
Run live, agent-driven end-to-end QA for os-clovy by opening the real app or web preview, clicking through changed flows, inspecting visible state, recording and compressing video, attaching QA videos to PRs through os-platform file uploads, capturing screenshots/logs, and reporting pass/fail evidence. Use when a user…