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/wangyendt/wayne-skills/cmdloggernpx skills add wangyendt/wayne-skills --skill cmdloggergit clone --depth 1 https://github.com/wangyendt/wayne-skillsWrote 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/wangyendt/wayne-skills/cmdlogger)<a href="https://agentmods.dev/skills/wangyendt/wayne-skills/cmdlogger"><img src="https://agentmods.dev/badge/skills/wangyendt/wayne-skills/cmdlogger.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 | $0.00077 | $0.00812 |
| Opus 5 | $0.00039 | $0.00406 |
| Sonnet 5 | $0.00015 | $0.00162 |
| Haiku 4.5 | $0.00008 | $0.00081 |
Grade A, and why
pywayne-bin-cmdlogger 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.
# Log curl request with verbose output How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pywayne Bin Cmdlogger
Execute a command and log all stdin, stdout, stderr to a file while forwarding I/O to console in real-time.
Quick Start
# Log command execution to default file (io_log.log in script directory)
cmdlogger <command> [args...]
# Specify custom log file path
cmdlogger --log-path <log_path> <command> [args...]
Usage Examples
Build Process Recording
# Log CMake configuration
cmdlogger --log-path cmake_config.log cmake ..
# Log build process
cmdlogger --log-path build.log make -j$(nproc)
Script Execution Monitoring
# Log Python script execution
cmdlogger --log-path script_run.log python3 my_script.py --arg1 value1
# Log shell script execution
cmdlogger --log-path deploy.log ./deploy.sh production
Debugging Sessions
# Log GDB debug session
cmdlogger --log-path debug_session.log gdb ./my_program
# Log Python interactive session
cmdlogger --log-path python_debug.log python3 -i my_module.py
Network Operations
# Log curl request with verbose output
cmdlogger --log-path api_test.log curl -v https://api.example.com/data
# Log SSH connection process
cmdlogger --log-path ssh_session.log ssh user@remote-host
Simple Command Logging
# Log git status
cmdlogger git status
# Log echo command
cmdlogger echo "Hello World"
Command Reference
| Argument | Description |
|---|---|
command |
The command to execute |
[args...] |
Command arguments |
--log-path <path> |
Optional log file path. Default: io_log.log in script directory |
Log Format
Each line in the log file is prefixed with stream type:
输入: <content>- Standard input输出: <content>- Standard output错误: <content>- Standard error
Example Log Output
Running cmdlogger echo "Hello World" produces:
输出: Hello World
Running cmdlogger python3 -c "import sys; print('stdout'); print('stderr', file=sys.stderr)" produces:
输出: stdout
错误: stderr
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 · 125 lines · 77 tokens per session scan A 03e513c2d053
pywayne-bin-cmdlogger is a skill published in the GitHub repository wangyendt/wayne-skills (8 stars, last pushed 8d ago), licensed MIT. It adds 77 tokens to every session and 812 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…