Banned API Audit

What it does

Example prompts

• “/banned-api-audit”

Requirements

• Node.js
• A Bash shell

Workflow steps

6 steps, taken from the step headings in SKILL.md.

1. 1Resolve banlist
2. 2Resolve paths and exclusions
3. 3Scan with ripgrep
4. 4Honor inline allow annotations
5. 5Emit report
6. 6Exit code

What it can do on your machine

Read from SKILL.md and the folder at commit dda238f. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships 2 files in scripts/ (JavaScript and Shell), which the agent can run.

  Shell commands in SKILL.md call:

  • rg

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Links to these hosts (documentation or services it may open):

  • curl.se
  • github.com
  • docs.oasis-open.org

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Banned API Audit loads about 2.2k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 546 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~41

When it runs · the whole SKILL.md, loaded when a task matches

~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jmagly/aiwg at commit dda238f, republished under its MIT licence (© jmagly). 546 words, ~2,156 tokens.

name

banned-api-audit

description

Scan source code for banned APIs/forbidden functions per project banlist; report violations with paths, line numbers, and recommended replacements

namespace

aiwg

platforms

all

invariants

inline AIWG-allow annotations are honored and recorded in the report (never silently dropped), test/**, tests/**, vendor/**, node_modules/**, .aiwg/**…

script.entrypoint

scripts/audit.mjs

script.runtime

node

script.cwd

project-root

script.argsHint

[--starter c|cpp|python|node|go|rust] [--fail-on-violation] [--paths <path>...] [--format text|json|both|sarif]

commandHint.argumentHint

[--starter c|cpp|python|node|go|rust] [--fail-on-violation] [--paths <glob>...] [--format text|json|both|sarif] [--sarif]

commandHint.allowedTools

Read, Write, Bash, Glob, Grep

commandHint.model

haiku

# Word-boundary literal pattern
rg -n --type <lang> -w '<pattern>' <paths>

# Regex pattern (when prefixed re:)
rg -n --type <lang> '<regex>' <paths>

AIWG-allow:banned-apis reason="..."

Banned API Audit — 2026-05-21T17:30:00Z

Banlist:    .aiwg/security/banned-apis.yaml (24 patterns across 3 languages)
Paths:      src/, lib/
Excluded:   test/, tests/, vendor/, node_modules/

VIOLATIONS (3)

src/auth/token.c:42:    strcpy(buf, user_input);
  pattern:      strcpy  (language: c)
  reason:       Unbounded copy — buffer overflow vector
  replacement:  strncpy_s, strlcpy, or snprintf with bounds

src/parser/json.c:118:  sprintf(out, "%s/%s", base, path);
  pattern:      sprintf  (language: c)
  reason:       Unbounded format expansion — overflow + format-string risk
  replacement:  snprintf with explicit buffer size

src/util/legacy.py:7:   user = pickle.loads(payload)
  pattern:      re:pickle\.loads?\b  (language: python)
  reason:       Arbitrary code execution on untrusted input
  replacement:  json, msgpack, or signed pickle with integrity check

EXCEPTIONS (1)

src/compat/curses_wrapper.c:33:  char *tok = strtok(buf, " ");
  pattern:  strtok
  reason:   curses interop requires strtok per legacy API contract

SUMMARY
  Violations:  3
  Exceptions:  1
  Patterns:    24
  Files scanned: 184

{
  "schemaVersion": "1",
  "auditedAt": "2026-05-21T17:30:00Z",
  "banlistPath": ".aiwg/security/banned-apis.yaml",
  "patterns": 24,
  "filesScanned": 184,
  "violations": [
    {
      "file": "src/auth/token.c",
      "line": 42,
      "column": 5,
      "match": "strcpy(buf, user_input);",
      "pattern": "strcpy",
      "language": "c",
      "reason": "Unbounded copy — buffer overflow vector",
      "replacement": "strncpy_s, strlcpy, or snprintf with bounds",
      "severity": "HIGH"
    }
  ],
  "exceptions": [ /* same shape, plus exceptionReason */ ]
}

- name: Banned-API audit
  run: aiwg run skill banned-api-audit -- --fail-on-violation

- name: Banned-API audit
  run: aiwg run skill banned-api-audit -- --fail-on-violation

© jmagly, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (scripts) in agentic/code/plugins/security-engineering/skills/banned-api-audit of jmagly/aiwg.

• SKILL.md
• banlists/c.yaml
• banlists/cpp.yaml
• banlists/go.yaml
• banlists/node.yaml
• banlists/python.yaml
• banlists/rust.yaml
• schema.json
• scripts/audit.mjs
• scripts/audit.sh

Open the folder on GitHubat commit dda238f