agentmods.dev

specship

A settings file that limits an agent to nine named command patterns, mainly for testing, packaging, publishing previews, and checking Git history or changes.

In plain words
What is it for?
Use it to define allowed commands for running tests, previewing a package or publication, and inspecting repository status, differences, commits, and branches.
Why use it?
It restricts which commands the agent may run, reducing accidental work outside the intended project tasks.

Settings file for Claude Code

2 24d ago A scan tokens not measured original MIT
View the source file bonnguyenitc/specship
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.

agentmods
npx agentmods add settings/bonnguyenitc/specship/settings
Clone the repo
git clone --depth 1 https://github.com/bonnguyenitc/specship

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

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

.claude/settings.json · 16 lines

What it actually says

{
  "permissions": {
    "allow": [
      "Bash(npm test:*)",
      "Bash(node test/cli.test.js:*)",
      "Bash(node bin/cli.js:*)",
      "Bash(npm pack --dry-run:*)",
      "Bash(./publish.sh --dry-run:*)",
      "Bash(git status:*)",
      "Bash(git diff:*)",
      "Bash(git log:*)",
      "Bash(git branch:*)"
    ]
  }
}
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. 2d ago First seen · 16 lines scan A 5556ab6027f3

Subscribe to this mod's changes

specship is a settings file published in the GitHub repository bonnguyenitc/specship (2 stars, last pushed 24d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

Design and UXagentagent-skillsagent-workflowclaudecodecodexcoding
Related

Other settings, from other repositories

lastlight

Agent settings declaring 1 hook event (PreToolUse).

nearform/lastlight · not measured

scaffold

Agent settings declaring 3 hook events (SessionStart, PreToolUse, PostCompact).

victusfate/scaffold · not measured

helixent

Agent settings declaring 6 allowed tools.

MagicCube/helixent · not measured

settings

The Claude Code background agent for Linear, Slack, Github, GitLab etc. you deploy anywhere. Supports Codex, Cursor and Gemini too.

cyrusagents/cyrus · not measured

supabase

Agent settings declaring 2 hook events (SessionStart, PostToolUse).

supabase/supabase · not measured

superset

Agent settings declaring 1 hook event (PreToolUse).

apache/superset · not measured