Borrowing it
Nothing to install: this file belongs to abuango/pos-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/abuango/pos-ai/main/.claude/skills/architecture/SKILL.mdgit clone --depth 1 https://github.com/abuango/pos-aiWrote 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/abuango/pos-ai/architecture)<a href="https://agentmods.dev/skills/abuango/pos-ai/architecture"><img src="https://agentmods.dev/badge/skills/abuango/pos-ai/architecture.svg" alt="Measured on agentmods" 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.00050 | $0.00968 |
| Opus 5 | $0.00025 | $0.00484 |
| Sonnet 5 | $0.00010 | $0.00194 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
architecture 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 6d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Skill
Setup
Before starting: check .handoff/sessions/ for active sessions, read context status.yaml, run git status. Follow .rules/universal.md (Plan -> Approve -> Execute).
You are performing architecture design or review for a POS project. Architecture decisions are the hardest to reverse — measure twice, cut once.
Process
Step 1: Understand Context
- Identify the project — Read the project YAML and existing codebase
- Load existing architecture docs — Check for:
docs/architecture/ordocs/adr/in the repo- Existing
AGENTS.mdor system diagrams PROJECT_INDEX.yamlfor file structure overview
- Clarify scope — Is this a new system design, a review of existing architecture, or a change proposal?
Step 2: Analyze (Review Mode)
When reviewing existing architecture:
- Component boundaries — Are services/modules cohesive with minimal coupling?
- Data flow — Is data ownership clear? No circular dependencies?
- API contracts — Are interfaces between components well-defined?
- Scalability — Can the system handle 10x load without redesign?
- Single points of failure — Are there components whose failure cascades?
- Technology fit — Do chosen technologies match the problem domain?
- Security boundaries — Are trust zones and auth boundaries explicit?
- Operational concerns — Logging, monitoring, deployment, rollback?
Step 3: Design (Creation Mode)
When designing new architecture:
- Define constraints — Budget, team size, timeline, existing tech stack
- Identify key decisions — Database choice, communication patterns, hosting model
- Map components — Services, data stores, external integrations, client apps
- Define interfaces — API contracts between components
- Document trade-offs — Every decision has trade-offs; make them explicit
Step 4: Produce ADR
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 140 lines · 50 tokens per session scan A b1c68f58711b
architecture is a skill published in the GitHub repository abuango/pos-ai (2 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 968 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
make-resume
中文可编辑简历制作技能：默认基于 ASu 单栏高密度技术简历模板，根据用户经历制作或复刻可编辑 HTML/PDF；用户也可以指定仓库内其他模板、本地 HTML 或参考截图。用户输入“/make-resume”“我要阿酥同款简历”或要求制作、修改、复刻简历文件时使用。.
prototype-web
可点击的功能性 Web 原型, 含导航、英雄区、特性区、CTA.