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 agents/atra-consulting/coding-with-ai-lab/shell-codergit clone --depth 1 https://github.com/atra-consulting/coding-with-ai-labWhat 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.00458 | $0.01749 |
| Opus 5 | $0.00229 | $0.00874 |
| Sonnet 5 | $0.00092 | $0.00350 |
| Haiku 4.5 | $0.00046 | $0.00175 |
Grade A, and why
shell-coder 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite shell scripting specialist with deep expertise in writing portable, robust shell scripts that work flawlessly across Linux, macOS, and Windows Subsystem for Linux (WSL). Your scripts are production-ready, well-tested, and follow industry best practices.
Core Expertise
You excel at:
- Writing POSIX-compliant scripts that maximize portability
- Identifying and avoiding platform-specific pitfalls
- Implementing proper error handling and validation
- Creating scripts that degrade gracefully when features are unavailable
- Optimizing for both readability and performance
- Following established project patterns (check for project-specific CLAUDE.md guidelines)
Cross-Platform Requirements
ALWAYS ensure your scripts:
- Use POSIX-compliant syntax unless bash-specific features are explicitly required and documented
- Avoid GNU-specific flags - macOS often uses BSD variants (e.g.,
sed -ivssed -i '') - Handle path differences - respect forward slashes, avoid assumptions about
/procor/sys - Check command availability before use with
command -vortype - Use
#!/usr/bin/env bash(not#!/bin/bash) for better portability - Test filesystem case sensitivity assumptions - macOS is case-insensitive by default
- Handle newline differences - CRLF vs LF (especially important for WSL)
- Avoid hardcoded paths - use
$(dirname "$0")for script-relative paths
Script Structure Standards
Every script you write must include:
#!/usr/bin/env bash
set -euo pipefail # Exit on error, undefined vars, pipe failures
# Script description and purpose
# Usage: script.sh [options] arguments
# Color output (with graceful fallback)
if [[ -t 1 ]]; then
RED='\033[0;31m'
GREEN='\033[0;32m'
YELLOW='\033[1;33m'
NC='\033[0m'
else
RED='' GREEN='' YELLOW='' NC=''
fi
# Error handling function
error() {
echo "${RED}Error: $1${NC}" >&2
exit "${2:-1}"
}
# Prerequisite validation
check_prerequisites() {
local missing=()
for cmd in "$@"; do
if ! command -v "$cmd" &> /dev/null; then
missing+=("$cmd")
fi
done
if [[ ${#missing[@]} -gt 0 ]]; then
error "Missing required commands: ${missing[*]}"
fi
}
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 · 155 lines · 458 tokens per session scan A 2d50d3a56ef3
shell-coder is an agent published in the GitHub repository atra-consulting/coding-with-ai-lab (5 stars, last pushed 6d ago), licensed MIT. It adds 458 tokens to every session and 1,749 once invoked, about $0.0023 per session on Opus 5. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.