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/markmhendrickson/ateles/debugnpx skills add markmhendrickson/ateles --skill debuggit clone --depth 1 https://github.com/markmhendrickson/atelesWhat 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.00008 | $0.06800 |
| Opus 5 | $0.00004 | $0.03400 |
| Sonnet 5 | $0.00002 | $0.01360 |
| Haiku 4.5 | $0.00001 | $0.00680 |
Grade A, and why
debug 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 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
remoteUrl = execSync('git remote get-url origin', { cwd: repoPath }) This is a copy
97% identical to debug — 15 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 — 979 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Command
Purpose
Check for pending error reports and debug/resolve them. Supports cross-repo error queue checking for sibling repositories. Also manages the error debugging automation watcher.
Command Usage
/debug [action|target-repo-name]
Modes of Operation:
The command operates in two modes based on the first argument:
1. Watcher Management Mode
If the first argument is a watcher management action (start, stop, status, logs, restart), manage the error debugging automation watcher:
/debug start # Start the error debugging watcher
/debug stop # Stop the running watcher
/debug status # Check watcher status
/debug logs # Show watcher logs
/debug restart # Restart the watcher
2. Error Debugging Mode (Default)
If the first argument is not a watcher action (or no arguments provided), check and debug pending errors:
/debug # Check current repo's pending errors (default)
/debug neotoma # Check sibling repo's pending errors
/debug personal-project # Check another sibling repo
Note: To check watcher status, use /debug status. The default behavior (no arguments) checks for pending errors in the current repository.
Parameters:
action(optional): Watcher management action (start,stop,status,logs,restart)- If provided, manages the error debugging automation watcher
- If omitted: Defaults to error debugging mode (check pending errors)
target-repo-name(optional): Name of sibling repository to check for pending errors- Must be a sibling repository (shares same parent directory)
- Only used if first argument is not a watcher action
Examples:
# Watcher management
/debug start # Start watcher
/debug status # Check watcher status
/debug logs # View watcher logs
/debug stop # Stop watcher
# Error debugging
/debug # Check current repo's pending errors
/debug neotoma # Check sibling repo's pending errors
/debug --list-only # List errors without debugging
/debug --all --auto # Process all errors automatically
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 · 979 lines · 8 tokens per session scan A 722a8d8ec7ab
debug is a skill published in the GitHub repository markmhendrickson/ateles (5 stars, last pushed 4d ago), licensed MIT. It adds 8 tokens to every session and 6,800 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). It is 97% identical to debug, differing in 15 lines, and is treated as a copy.
Other skills, from other repositories
10x-orchestrator
MANDATORY - The core brain of 10X Vibe Marketer. You are the autonomous CMO orchestrating a full marketing agency of 12 specialist departments. Load this skill for ANY marketing task - content creation, SEO, campaigns, strategy, research, analytics, outreach, social media, email, paid ads, branding, funnel…
10x-setup
First-time setup and initialization for 10X Vibe Marketer. Includes an interactive wizard that lets users choose their database, features, marketing focus, visual tools, and tracking preferences. Checks setup.log to determine if setup has already been completed. Run via /setup or auto-triggered on first use.
10x-visualizer
Generate visual marketing deliverables — strategy boards, funnel diagrams, flowcharts, journey maps, dashboards, and more — using TLDraw SDK (local .tldr files). Each department agent creates visuals for their own domain. Invoke with /report.
10x-research
The research orchestration engine for 10X Vibe Marketer. Powers multi-platform, real-time research across 13 platforms using Claude in Chrome and WebSearch/WebFetch. Spawns platform-specific research agents in parallel, consolidates findings through the research lead, and delivers actionable marketing intelligence.
community-manager
Skill "community-manager" from OpenAnalystInc/Vibe-Marketer, covering community manager — 10x vibe marketer, identity, step-by-step execution, cli visual identity and expertise.
funnel-cro-specialist
Skill "funnel-cro-specialist" from OpenAnalystInc/Vibe-Marketer, covering funnel & cro specialist — 10x vibe marketer, identity, step-by-step execution, cli visual identity and expertise.