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 darellchua2/opencode-config-template --skill object-design-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/object-design-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/object-design-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/object-design-skill.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 211 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00028 | $0.03458 |
| Opus 5 | $0.00014 | $0.01729 |
| Sonnet 5 | $0.00006 | $0.00692 |
| Haiku 4.5 | $0.00003 | $0.00346 |
Grade A, and why
object-design-skill 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 4d 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 — 567 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I help you design objects with clear responsibilities and proper encapsulation:
- Identify Object Stereotypes: Classify objects as Information Holders, Structurers, Service Providers, Coordinators, Controllers, or Interfacers
- Design Value Objects: Create immutable objects for domain primitives (IDs, emails, money)
- Design Entities: Create objects with identity that persist through changes
- Apply Tell Don't Ask: Command objects instead of interrogating them
- Design Aggregates: Create clusters of objects with consistency boundaries
- Apply Composition over Inheritance: Prefer composing objects over extending classes
When to use me
Use this skill when:
- Designing new classes or modules
- Refactoring classes that have unclear responsibilities
- Creating domain models for business concepts
- Deciding between value objects and entities
- Implementing domain-driven design patterns
- Reducing coupling between objects
- Improving encapsulation and information hiding
Prerequisites
- Understanding of object-oriented programming
- Knowledge of the business domain
- Familiarity with interfaces and abstractions
- Understanding of immutability concepts
Responsibility-Driven Design (RDD)
The key insight: Objects are defined by their responsibilities, not their data.
Finding Objects
Start with:
- Nouns in requirements → candidate objects
- Verbs → candidate methods/behaviors
- Domain concepts → value objects
Finding Responsibilities
Each object should answer:
- What does this object know?
- What does this object do?
- What does this object decide?
Object Stereotypes
Every class fits one (or maybe two) stereotypes:
| Stereotype | Purpose | Example |
|---|---|---|
| Information Holder | Knows things, holds data | User, Product, Address |
| Structurer | Maintains relationships | OrderItems, UserGroup |
| Service Provider | Performs work | PaymentProcessor, EmailSender |
| Coordinator | Orchestrates workflow | OrderFulfillmentService |
| Controller | Makes decisions, delegates | CheckoutController |
| Interfacer | Transforms between systems | UserAPIAdapter, DatabaseMapper |
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.
- 4d ago First seen · 567 lines · 28 tokens per session scan A fed5d3997355
object-design-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 28 tokens to every session and 3,458 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
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
llm-friendly-context
Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
megalinter-check
Collect MegaLinter lint errors for the current repository. Use when the user wants to know if the code passes linting, why the MegaLinter CI job fails, or before/after fixing lint errors. Two modes - watch a CI job (GitHub Actions, GitLab CI, Azure Pipelines, Bitbucket Pipelines) and parse its logs, or run MegaLinter…
bestie-features
Add BestieTemplate features (AGENTS.md, changelog, dependabot, pre-commit, lint workflow, testitem runner) to a Julia package with the bestie CLI — no Julia needed. Use when asked to add one of these files/setups to a package, or to see what BestieTemplate can add.