api-security-best-practices

api-security-best-practices is a skill for Claude Code from Ghosteken/agent-harness. It costs 29 tokens per session (5,955 once invoked), scanned A, a copy of api-security-best-practices, MIT.

A guide for turning existing software, scripts, or command-line tools into Apify Actors. An Actor is a cloud program packaged in a container that accepts JSON input and can return structured JSON output.

In plain words
What is it for?
Use it to add the Apify SDK, define input settings, test a wrapped program, migrate Crawlee projects, and deploy the result.
Why use it?
It explains the project changes needed to run existing code on Apify instead of rebuilding the software from scratch.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the agent-harness plugin — 173 skills, 17 commands, 12 agents shipped together

Good fit Use it to add the Apify SDK, define input settings, test a wrapped program, migrate Crawlee projects, and deploy the result.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ghosteken/agent-harness/api-security-best-practices
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 Ghosteken/agent-harness --skill api-security-best-practices
Clone the repo
git clone --depth 1 https://github.com/Ghosteken/agent-harness

Made for: Claude Code.

Or install agent-harness, the plugin that ships this one along with the rest of its 173 skills, 17 commands, 12 agents.

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 api-security-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/skills/ghosteken/agent-harness/api-security-best-practices/github.svg)](https://agentmods.dev/skills/ghosteken/agent-harness/api-security-best-practices)
Your own site
<a href="https://agentmods.dev/skills/ghosteken/agent-harness/api-security-best-practices"><img src="https://agentmods.dev/badge/skills/ghosteken/agent-harness/api-security-best-practices/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 api-security-best-practices

Your own site · 80×15
<a href="https://agentmods.dev/skills/ghosteken/agent-harness/api-security-best-practices"><img src="https://agentmods.dev/badge/skills/ghosteken/agent-harness/api-security-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,955 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 94% copy Near-identical to another mod 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.00029 $0.05955
Opus 5.5 $0.00012 $0.02382
Sonnet 5.5 $0.00006 $0.01191
Haiku 4.5 $0.00003 $0.00596

Measured 1mo ago against content hash 93902629949b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

api-security-best-practices 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 1mo 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.

Origin

This is a copy

94% identical to api-security-best-practices — 1,016 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

archive/skills-community/api-security-best-practices/SKILL.md · 916 lines

How it starts

The opening of the file, as written. The whole thing — 916 lines — stays where its author put it; the contents beside it link to each section on GitHub.

API Security Best Practices

Overview

Guide developers in building secure APIs by implementing authentication, authorization, input validation, rate limiting, and protection against common vulnerabilities. This skill covers security patterns for REST, GraphQL, and WebSocket APIs.

When to Use This Skill

  • Use when designing new API endpoints
  • Use when securing existing APIs
  • Use when implementing authentication and authorization
  • Use when protecting against API attacks (injection, DDoS, etc.)
  • Use when conducting API security reviews
  • Use when preparing for security audits
  • Use when implementing rate limiting and throttling
  • Use when handling sensitive data in APIs

How It Works

Step 1: Authentication & Authorization

I'll help you implement secure authentication:

  • Choose authentication method (JWT, OAuth 2.0, API keys)
  • Implement token-based authentication
  • Set up role-based access control (RBAC)
  • Secure session management
  • Implement multi-factor authentication (MFA)

Step 2: Input Validation & Sanitization

Protect against injection attacks:

  • Validate all input data
  • Sanitize user inputs
  • Use parameterized queries
  • Implement request schema validation
  • Prevent SQL injection, XSS, and command injection

Step 3: Rate Limiting & Throttling

Prevent abuse and DDoS attacks:

  • Implement rate limiting per user/IP
  • Set up API throttling
  • Configure request quotas
  • Handle rate limit errors gracefully
  • Monitor for suspicious activity

Step 4: Data Protection

Secure sensitive data:

  • Encrypt data in transit (HTTPS/TLS)
  • Encrypt sensitive data at rest
  • Implement proper error handling (no data leaks)
  • Sanitize error messages
  • Use secure headers

Step 5: API Security Testing

Verify security implementation:

  • Test authentication and authorization
  • Perform penetration testing
  • Check for common vulnerabilities (OWASP API Top 10)
  • Validate input handling
  • Test rate limiting

Examples

Example 1: Implementing JWT Authentication

Read the full file on GitHub · 916 lines

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. 1mo ago First seen · 916 lines · 29 tokens per session scan A 93902629949b

Subscribe to this mod's changes

api-security-best-practices is a skill published in the GitHub repository Ghosteken/agent-harness (4 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 5,955 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to api-security-best-practices, differing in 1,016 lines, and is treated as a copy.

Related

Other skills, from other repositories

sandy-cli

Run TypeScript scripts in sandboxed microVMs or Docker containers with AWS SDK access via IMDS, through the sandy CLI. Use when investigating AWS resources, running read-only queries, or executing TypeScript automation that needs AWS credentials via shell commands.

jamestelfer/sandy · 54 tokens

cao-provider

Create a new CLI agent provider for CAO (CLI Agent Orchestrator). Use this skill whenever the user wants to add support for a new CLI-based AI agent (e.g., a new coding assistant CLI), integrate a new provider, or scaffold a provider implementation. Also use when the user asks about the provider architecture, what…

awslabs/cli-agent-orchestrator · 81 tokens

enterprise

Enterprise-grade systems with microservices, Kubernetes, Terraform, and AI Native methodology. For multi-feature initiatives spanning a release timeline, combine with /sprint master-plan (v2.1.13) to group features into a single 8-phase sprint container with shared scope/budget and 4 auto-pause triggers…

ww-w-ai/bkit-claude-code · 106 tokens

supabase

Complete guide for the Supabase plugin — Management API access for running SQL queries, listing projects, managing edge functions, secrets, migrations, and inspecting project health.

stagewise-io/stagewise · 35 tokens

api-provider-setup

A set of instructions for adding third-party API providers to OpenClaw, an agent platform, through custom model endpoints that follow Anthropic- or OpenAI-compatible formats.

aAAaqwq/AGI-Super-Team · 63 tokens

multi-app-orchestration

Orchestrate workflows across multiple applications and APIs — inter-app coordination, data handoff, and multi-system task completion.

a5c-ai/babysitter · 30 tokens