coding

A set of Appie standards for making code changes small, readable, maintainable, tested, and consistent with the existing project.

In plain words
What is it for?
Use it when writing or reviewing code, especially to validate input handling, error reporting, secrets, unfinished work, consistent style, and test coverage.
Why use it?
AI-generated changes can introduce unnecessary refactoring, hidden behavior, missing error handling, or security mistakes. These checks help keep implementation work controlled.

Skill for Claude CodeCodex

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 skills/s3yed/appie-kit/coding
Any agent
npx skills add S3YED/appie-kit --skill coding
Clone the repo
git clone --depth 1 https://github.com/S3YED/appie-kit

Made for: Claude Code, Codex.

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,090 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original 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 $0.00025 $0.02090
Opus 5 $0.00013 $0.01045
Sonnet 5 $0.00005 $0.00418
Haiku 4.5 $0.00003 $0.00209

Measured 2d ago against content hash 087a98c70984, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

coding scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

const response = await fetch(url, {
skills/automation/coding/SKILL.md · 392 lines

How it starts

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

Coding Skill

How Appies write code

Purpose

Guidelines and prompts for writing high-quality, maintainable code.


Core Principles

1. Minimal Invasion

  • Change only what's necessary
  • Preserve existing patterns
  • Don't refactor unless required
  • Leave working code alone

2. Readability First

// ❌ Clever
const x = data.reduce((a,b)=>({...a,[b.k]:b.v}),{});

// ✅ Clear
const result = {};
data.forEach(item => {
  result[item.key] = item.value;
});

3. Explicit Over Implicit

// ❌ Magic
const users = await db.get('users');

// ✅ Clear
const users = await database.users.findAll({ 
  where: { active: true },
  limit: 100 
});

4. Error Handling

// Always handle errors
try {
  const result = await riskyOperation();
  return { ok: true, result };
} catch (error) {
  console.error('Operation failed:', error.message);
  return { ok: false, error: error.message };
}

Code Quality Checklist

Before committing code, check:

  • No hardcoded secrets - Use env vars
  • Input validation - Check all external inputs
  • Error handling - Try/catch with meaningful messages
  • No TODOs - Fix or document separately
  • Consistent style - Match existing code
  • Clear names - Variables/functions describe purpose
  • One thing per function - Single responsibility
  • Comments explain WHY - Not what (code shows what)

Appie Coding Prompt

When writing code, follow this structure:

1. Understand Requirements

What problem am I solving?
What are the inputs?
What are the outputs?
What are the edge cases?

2. Check Existing Code

# Find similar implementations
grep -r "similar_function" .
# Read before reimplementing

3. Write Simple First

// Start with the simplest solution
function processData(data) {
  // Basic happy path
  if (!data) return null;
  return data.map(item => item.value);
}

4. Add Error Handling

function processData(data) {
  if (!data) {
    console.error('processData: data is required');
    return { ok: false, error: 'Data required' };
  }
  
  try {
    const result = data.map(item => {
      if (!item.value) throw new Error('Missing value');
      return item.value;
    });
    return { ok: true, result };
  } catch (error) {
    console.error('processData failed:', error.message);
    return { ok: false, error: error.message };
  }
}

Read the full file on GitHub · 392 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. 2d ago First seen · 392 lines · 25 tokens per session scan A 087a98c70984

Subscribe to this mod's changes

coding is a skill published in the GitHub repository S3YED/appie-kit (6 stars, last pushed 6d ago), licensed MIT. It adds 25 tokens to every session and 2,090 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

seo-geo-optimizer

Comprehensive SEO/GEO/AEO analysis toolkit for optimizing content visibility across traditional search engines (Google, Bing), AI platforms (ChatGPT, Perplexity, Claude, Gemini, Grokipedia), answer engines (Google AI Overviews, Bing Copilot, featured snippets), voice assistants (Google Assistant, Siri, Alexa), and…

ViryaZheng/recomby-geo · 121 tokens

internal-linking-optimizer

Use when improving internal link structure, anchor text, orphan pages, crawl depth, site architecture, or link equity flow. 内链优化/站内架构.

ViryaZheng/recomby-geo · 38 tokens

geo-pipeline

Entry point + orchestrator for the recomby-geo GEO (Generative Engine Optimization) workflow on OpenAI Codex CLI. Use when the user wants to run any stage of the GEO pipeline on a client folder — intake, visibility audit, content-gap analysis, content brief, draft production, distribution, or monthly re-audit — or…

ViryaZheng/recomby-geo · 169 tokens

geo-review-html

Render an interactive, self-contained HTML companion for a GEO content brief (04-content-brief) or a publish-ready draft (05-production), so a NON-technical client reviewer (founder, organizer staff, the domain expert filling slots) can fill REQUIRED-FILL slots, leave section-level comments, and approve/return work in…

ViryaZheng/recomby-geo · 140 tokens

follow-up-writer

Use when drafting a post-event follow-up message to someone met at a conference.

staruhub/CrewClaw · 21 tokens

schedule

Create, list, remove or inspect this bot's scheduled work — recurring jobs ("every morning at 7 tell me X", "every weekday at 9 post the standup") and one-shot follow-ups ("check back in 20 minutes", "watch that deploy until it lands", "remind me on Friday"). Use whenever something must happen on a schedule…

xrgarcia/slashbin-ai-team · 92 tokens