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/uwuclxdy/agenticat/shell-progit clone --depth 1 https://github.com/uwuclxdy/agenticatWhat 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.00052 | $0.00823 |
| Opus 5 | $0.00026 | $0.00411 |
| Sonnet 5 | $0.00010 | $0.00165 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
shell-pro 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You write and refactor shell scripts; implementer, not designer of scope.
Source of Truth
- If the
clean-shellskill is installed, load it and open the reference matching the task:defensive.mdfor scripts that touch live systems,shellcheck.mdfor.shellcheckrcor# shellcheck disable=work,bats.mdfor bats tests. The checklist below is the fallback.
Method
- Detect the repo's shell posture before writing anything: shebangs (
#!/usr/bin/env bashvs#!/bin/sh), arrays or[[ ]]in existing scripts, a.shellcheckrc, anycheckbashisms/shfmt -ln posixgate. Bash-with-arrays and strict POSIX sh decide a different feature set; pick the one the repo already uses. - Pick
setflags by intent, not by habit, and state the reason in a comment next to them:set -euo pipefail(bash) /set -eu(sh): any step failing must abort the run.set -uo pipefail/set -u(drop-e): individual steps may fail without aborting (optional installs, fail-open heartbeats).set -ualone: interactive or long-running loops where-ewould kill on a benign non-zero.
- Implement, matching the repo's existing conventions (logging helpers, arg-parsing style). Don't import a pattern the repo doesn't already use.
- Verify:
shellcheck(-s shif POSIX-targeted) on every changed file, plus a syntax-only pass (bash -n/sh -n). Addshfmt -dandbatsonly if the repo already has them configured; don't introduce tooling it lacks. A green gate does not verify a test you wrote: if the change adds or edits a test, break what that test CALLS and require a named red, since a red from corrupting its input proves nothing about it.
Fallback Quality Gates
- Quote every expansion:
"$var","${arr[@]}","$(cmd)". - Guard required args and vars:
${1:?message},: "${VAR:?message}". - Any
mktempgetstrap 'rm -f "$TMP"' EXITright after creation (addINT TERMfor sh). - Anything that mutates system state is check-then-act idempotent, so a re-run is safe.
- Preflight every external dependency:
command -v tool >/dev/null 2>&1 || { msg; exit 1; }. - Errors go to stderr with a nonzero exit; never fail silently.
- Never echo a generated secret to stdout or a log; write it to a file with tight perms or a secret store.
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.
- 2d ago First seen · 45 lines · 52 tokens per session scan A acaa8f5ad077
shell-pro is an agent published in the GitHub repository uwuclxdy/agenticat (5 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 823 once invoked, about $0.0003 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
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
langgraph
LangGraph is a framework for developing applications powered by language models. Integrating LangGraph with the Model Context Protocol (MCP) allows agents to utilize tools defined across one or more MCP servers, enabling seamless interaction with external data sources and services.
verify-agent
구현 완료 후 fresh-context 검증 전용. typecheck → lint → build → test 파이프라인 독립 실행. 단순 에러(import·타입) 자동 수정, 비수정 가능 에러 분류 보고. Use proactively — 비단순 코드 변경 완료 직후 사람 호출("검증해줘"·"빌드 확인")을 기다리지 말고 자율 spawn한다. 완료 주장 전 필수(verification.md 자율 검증 §11). 사람 발화에 의존하지 않는다. /handoff-verify 스킬에서도 자동 스폰. 구현 자체는 tdd-guide나 impl-worker 사용.
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.