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/ralfstrobel/agentic-brownfield-coding/bashlessnpx skills add ralfstrobel/agentic-brownfield-coding --skill bashlessgit clone --depth 1 https://github.com/ralfstrobel/agentic-brownfield-codingWhat 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.00026 | $0.03278 |
| Opus 5 | $0.00013 | $0.01639 |
| Sonnet 5 | $0.00005 | $0.00656 |
| Haiku 4.5 | $0.00003 | $0.00328 |
Grade B, and why
bashless scanned grade B 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 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- Use `run_local_sandboxed` for all tools that locally execute arbitrary code or filesystem operations. How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Bashless Setup
Your goal is to amend an existing Claude Code project setup so that the agent no longer uses
the built-in Bash tool. Instead, all essential CLI capabilities are exposed as structured MCP tools
via a local MCP stdio server. This forces the agent to use purpose-built tools with explicit parameters
rather than being attracted to unstructured shell access.
Additional user arguments: $ARGUMENTS
Language hint: Always create all generated script content and comments in English, while continuing to speak to the user in the language of their choice.
Platform hint: Instructions and templates assume a Linux host with GNU coreutils. Adapt to the detected user OS.
- macOS — Substitute BSD equivalents for GNU-only utilities.
- Windows — Still use
.shfiles (skip irrelevantchmod +x), assuming Git Bash is available at runtime. Highlight this requirement in the Debriefing. Set"shell": "bash"on new command hooks insettings.json. Launch the MCP server via bash rather than putting the.shpath directly incommand.
Workflow
- Begin execution by creating a formal task list for progress tracking using the
TaskCreatetool. Create a task for each of the following phases (##) and sub-phases (###). Do not duplicate the contents in the description, only reference this skill (abc-init:bashless) and the workflow item. - Create a dependency chain between all tasks using
TaskUpdate, settingaddBlockedByto the predecessor task. - Work through the
TaskListusingTaskUpdateto mark tasks as in_progress and completed as you go.
Phase 1: Reconnaissance
Catalogue shell commands and MCP tools the agent will require during autonomous code development for this project. Assume the project has already been initialized with artifacts for Claude Code and existing technology is documented.
1a — Shell Commands
Spawn an Agent to scan the following locations for explicit and implicit references to CLI commands:
- The project's
CLAUDE.mdand any sub-directoryCLAUDE.mdfiles - The project's
.claudedirectory, particularly sub-directoriescommands/,rules/andagents/ - Top-level documentation files (e.g.
README.md,CONTRIBUTING.md,docs/)
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.
- 2d ago First seen · 232 lines · 26 tokens per session scan B 20bd65997e58
bashless is a skill published in the GitHub repository ralfstrobel/agentic-brownfield-coding (28 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 3,278 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
manager
Sync session work into GitHub issues, or query track status across repos. Write: find/update issue + W-label. Read: "что по ". Triggers: "создай issue", "синкни сессию", "manager". Not day/week plans (daily-tasks).
weekly-retro
Use when the user is closing an ISO week, reviewing planned outcomes against evidence, interviewing work Areas, resolving unfinished commitments, or asking for "ретро", "weekly retro", "week review", or lessons from the week.
art-director
Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.
html-draft
Use when user wants a standalone HTML diagram in flat engineering blueprint style — architecture diagrams, system flows, technical spec sheets, component maps. Generates one HTML file using Tailwind v4 (browser CDN) for layout and D3 v7 (CDN) for SVG diagrams. User-invoked only — do NOT auto-trigger. Triggers on…
pm-metrics
Делает ревью продуктовых метрик — тренды, аномалии, root causes и рекомендации к действиям. Включает декомпозицию North Star (L1/L2), диагностику retention-кривых, анализ воронки, разбор A/B-экспериментов, проверку соответствия OKR и фреймворк атрибуции аномалий. User-invoked only — do NOT auto-trigger. Triggers on…
corp-doctor
Use when a Personal Corp operating loop needs setup, repair, a new department, or task routing: HQ files and agent rules, GitHub issue workflow, corp- owner map, department repositories, or deciding which repo an issue belongs to. Triggers: "corp doctor", "почини контур", "заведи отдел", "куда положить задачу"…