Borrowing it
Nothing to install: this file belongs to jonathan-vella/apex-accelerator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jonathan-vella/apex-accelerator/main/.github/instructions/shell.instructions.mdgit clone --depth 1 https://github.com/jonathan-vella/apex-acceleratorWrote 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.
[](https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/shell)<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/shell"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/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.
<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/shell"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/shell.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00512 | $0.00512 |
| Opus 5.5 | $0.00205 | $0.00205 |
| Sonnet 5.5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
apex-accelerator shell.instructions.md 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 6d 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.
What it actually says
Shell Scripting Guidelines
Quick Reference
| Rule | Standard |
|---|---|
| Shebang | #!/usr/bin/env bash (Bash) or #!/bin/sh (POSIX) |
| Safety | set -euo pipefail (Bash) or set -eu (POSIX sh) |
| Variables | Double-quote: "$var"; use ${var} for clarity; avoid eval |
| Cleanup | trap cleanup EXIT for temp files/resources |
| Constants | readonly SCRIPT_NAME="$(basename "$0")" |
| Temp files | mktemp — never hardcode temp paths |
| JSON/YAML | Use jq/existing js-yaml tooling, not text-processing hacks |
| Conditionals | [[ ]] in Bash; [ ] only for POSIX portability |
Script Structure
- Header comment explaining purpose
- Use
set -euo pipefailfor Bash; useset -eufor POSIX sh trap cleanup EXITfor resource teardown- Default variables at top; functions next;
maincalled at bottom - Validate required parameters before execution
- Clear, concise
echofor status — avoid excessive logging
Working with Structured Data
- Prefer
jqfor JSON. For YAML, use a committed Node.js helper with the existingjs-yamldependency;yqis not provisioned or required by APEX. - Reuse
parseFrontmatterfor Markdown frontmatter andjs-yamlfor full YAML documents. Runnpm cito provision the lockfile-pinned Node tooling before using it. - Validate required fields; treat parser errors as fatal
- Quote
jqfilters; use--raw-outputfor plain strings - Document parser dependencies at script top; fail fast if absent
Argument Parsing
For Bash, use while [[ $# -gt 0 ]]; do case $1 in ...; for POSIX sh,
use while [ "$#" -gt 0 ]; do case $1 in .... Use shift for each
option and include -h|--help with a usage() function.
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.
- 6d ago Changed · +3 lines · +63 tokens per session 47cf0edd9837
- 1mo ago Changed · +1 lines · +35 tokens per session 00afd416a6bb
- 1mo ago First seen · 41 lines · 414 tokens per session scan A cd20e996d298
apex-accelerator shell.instructions.md is an instructions file published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 512 tokens to every session, about $0.0020 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-03.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.