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.
npx skills add fabioc-aloha/Alex_Skill_Mall --skill defaults-plus-overridesgit clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_MallWrote 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/skills/fabioc-aloha/alex_skill_mall/defaults-plus-overrides)<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/defaults-plus-overrides"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/defaults-plus-overrides/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/skills/fabioc-aloha/alex_skill_mall/defaults-plus-overrides"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/defaults-plus-overrides.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.00021 | $0.01232 |
| Opus 5 | $0.00010 | $0.00616 |
| Sonnet 5 | $0.00004 | $0.00246 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
defaults-plus-overrides 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Defaults Plus Overrides
Category: Architecture Time Saved: 2+ hours avoiding configuration complexity Battle-tested: Yes — user preference systems, role-based config
The Problem
You're building a system with configurable behavior — user preferences, role-based permissions, or tenant-specific settings. You need sensible defaults but also flexibility. You end up with either rigid presets OR overwhelming configuration options.
Why It's Hard
- Too rigid: Users can't customize what they need
- Too flexible: Users must configure everything
- Presets only: Edge cases require workarounds
- Full config: Decision fatigue, misconfiguration risk
The Rule
Provide role/archetype defaults, allow partial overrides, clamp to safe bounds.
The Pattern
Archetype Default + User Overrides + Bounds Clamping = Final Config
Step 1: Define Archetypes
const ARCHETYPES = {
developer: {
verbosity: 'detailed',
theme: 'dark',
shortcuts: true,
maxTokens: 4000,
autoSave: true,
},
executive: {
verbosity: 'concise',
theme: 'light',
shortcuts: false,
maxTokens: 1000,
autoSave: false,
},
researcher: {
verbosity: 'detailed',
theme: 'auto',
shortcuts: true,
maxTokens: 8000,
autoSave: true,
},
};
Step 2: Define Bounds
const BOUNDS = {
maxTokens: { min: 100, max: 16000 },
verbosity: ['concise', 'normal', 'detailed'],
theme: ['light', 'dark', 'auto'],
};
Step 3: Merge with Clamping
function resolveConfig(archetype, overrides = {}) {
// Start with archetype defaults
const base = { ...ARCHETYPES[archetype] };
// Apply user overrides
const merged = { ...base, ...overrides };
// Clamp to bounds
return clampConfig(merged, BOUNDS);
}
function clampConfig(config, bounds) {
const result = { ...config };
for (const [key, constraint] of Object.entries(bounds)) {
if (constraint.min !== undefined) {
// Numeric bound
result[key] = Math.max(constraint.min, Math.min(constraint.max, result[key]));
} else if (Array.isArray(constraint)) {
// Enum bound
if (!constraint.includes(result[key])) {
result[key] = constraint[0]; // Default to first option
}
}
}
return result;
}
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.
- 8d ago First seen · 203 lines · 21 tokens per session scan A f6c6efbb2e09
defaults-plus-overrides is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 1,232 once invoked, about $0.0001 per session on Opus 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 skills, from other repositories
azure-storage
UTILITY SKILL — Azure Storage Services: Blob, File Shares, Queue, Table, and Data Lake. Object storage, SMB shares, async messaging, NoSQL key-value, big-data analytics. Access tiers + lifecycle management. WHEN: "blob storage", "file shares", "queue storage", "table storage", "data lake", "access tiers", "lifecycle…
api-design
REST API contract designer and reviewer. ALWAYS use when designing new endpoints, reviewing existing API contracts, planning API versioning, or standardizing error models. Covers resource modeling (URL/naming), HTTP method semantics, status code selection, error model consistency, pagination/filtering/sorting…
api-cms-payload
Payload CMS v3 — TypeScript-native headless CMS with code-first collections, hooks, access control, Local/REST/GraphQL APIs, admin panel, and database adapter pattern.
api-auth-clerk
Clerk managed authentication - ClerkProvider, middleware, pre-built components, hooks, server-side auth, organizations, webhooks.
api-cms-sanity
Structured content platform — GROQ queries, schema definitions, @sanity/client, Portable Text, image handling, real-time listeners, mutations, TypeGen.
api-database-postgresql
Direct PostgreSQL access with node-postgres (pg) -- connection pools, parameterized queries, transactions, streaming, LISTEN/NOTIFY, error handling.