probe-allowed-tools-shell

probe-allowed-tools-shell is a skill for Claude Code from agent-ecosystem/agent-skill-implementation. It costs 39 tokens per session (318 once invoked), scanned A, original, CC-BY-4.0.

A benchmark skill for checking how a platform names the allowed shell tool.

In plain words
What is it for?
Use it when testing whether the bare name "shell" is accepted in an allowed-tools setting.
Why use it?
It helps identify naming differences when a platform accepts only certain tool names.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it when testing whether the bare name "shell" is accepted in an allowed-tools setting.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/agent-ecosystem/agent-skill-implementation/probe-allowed-tools-shell
Install

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.

Any agent
npx skills add agent-ecosystem/agent-skill-implementation --skill probe-allowed-tools-shell
Clone the repo
git clone --depth 1 https://github.com/agent-ecosystem/agent-skill-implementation

Made for: Claude Code.

Wrote 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.

agentmods badge for probe-allowed-tools-shell

README.md
[![agentmods](https://agentmods.dev/badge/skills/agent-ecosystem/agent-skill-implementation/probe-allowed-tools-shell/github.svg)](https://agentmods.dev/skills/agent-ecosystem/agent-skill-implementation/probe-allowed-tools-shell)
Your own site
<a href="https://agentmods.dev/skills/agent-ecosystem/agent-skill-implementation/probe-allowed-tools-shell"><img src="https://agentmods.dev/badge/skills/agent-ecosystem/agent-skill-implementation/probe-allowed-tools-shell/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for probe-allowed-tools-shell

Your own site · 80×15
<a href="https://agentmods.dev/skills/agent-ecosystem/agent-skill-implementation/probe-allowed-tools-shell"><img src="https://agentmods.dev/badge/skills/agent-ecosystem/agent-skill-implementation/probe-allowed-tools-shell.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 318 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.00318
Opus 5.5 $0.00016 $0.00127
Sonnet 5.5 $0.00008 $0.00064
Haiku 4.5 $0.00004 $0.00032

Measured 23d ago against content hash 4ff8a699193f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

probe-allowed-tools-shell 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 23d 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.

benchmark-skills/probe-allowed-tools-shell/SKILL.md · 36 lines

The source is not reproduced here

Licensed CC-BY-4.0

The repository is licensed CC-BY-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. 23d ago First seen · 36 lines · 39 tokens per session scan A 4ff8a699193f

Subscribe to this mod's changes

probe-allowed-tools-shell is a skill published in the GitHub repository agent-ecosystem/agent-skill-implementation (6 stars, last pushed 22d ago), licensed CC-BY-4.0. It adds 39 tokens to every session and 318 once invoked, about $0.0002 per session on Opus 5.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-09-27.