Borrowing it
Nothing to install: this file belongs to dashpay/platform. 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/dashpay/platform/v5.1-dev/.claude/skills/layer-ownership/SKILL.mdgit clone --depth 1 https://github.com/dashpay/platformWrote 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/dashpay/platform/layer-ownership)<a href="https://agentmods.dev/skills/dashpay/platform/layer-ownership"><img src="https://agentmods.dev/badge/skills/dashpay/platform/layer-ownership/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/dashpay/platform/layer-ownership"><img src="https://agentmods.dev/badge/skills/dashpay/platform/layer-ownership.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.00053 | $0.00306 |
| Opus 5.5 | $0.00021 | $0.00122 |
| Sonnet 5.5 | $0.00011 | $0.00061 |
| Haiku 4.5 | $0.00005 | $0.00031 |
Grade A, and why
layer-ownership 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 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.
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.
What it actually says
Layer Ownership
Use during planning, implementation, and PR reviews. Treat every repository in
dashpay as an owned layer. Reviews are read-only unless the user requests
changes or comments.
Workflow
- Read
book/src/contributing/coding-conventions.mdcompletely from thedashpay/platformcheckout. - For planning, map each planned responsibility to its owner before naming
files. Inspect only the minimal existing boundary, callers, dependency
manifests, and owned
dashpayrepositories needed to settle placement. - During implementation, apply that placement and recheck the actual changed paths before handoff.
- For a PR, resolve exact base and head SHAs, then classify every changed path. Report only misplaced responsibilities, not unrelated issues.
Do not rescan unchanged subsystems. The conventions are authoritative.
Output
For every item, explicitly name current and target owner: repository,
crate/package, and module (current: new for new code). For PRs, lead with
pass or changes requested; each finding gives the file/line, misplaced
responsibility, and smallest move. State reviewed SHAs and unavailable evidence.
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.
- 2d ago First seen · 31 lines · 53 tokens per session scan A f205f3d961c9
layer-ownership is a skill published in the GitHub repository dashpay/platform (93 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 306 once invoked, about $0.0002 per session on Opus 5.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-10-28.
Other skills, from other repositories
analyzing-ransomware-payment-wallets
Traces ransomware cryptocurrency payment flows using blockchain analysis tools such as Chainalysis Reactor, WalletExplorer, and blockchain.com APIs. Identifies wallet clusters, tracks fund movement through mixers and exchanges, and supports law enforcement attribution. Activates for requests involving ransomware…
blockchain-web3
Use this skill when asked about web3 frontend development, ethers.js, viem, wagmi, web3.js, wallet integration (MetaMask, Phantom, WalletConnect), dApp architecture, RPC providers (Alchemy, Infura), and TypeScript blockchain SDKs. Language: TypeScript. Covers reading blockchain state, sending transactions, wallet…
frontend-design
Create distinctive, production-grade Stellar dApp UI. Combines bold aesthetic direction with smart contract integration patterns — wallet connection flows, transaction UX, contract data displays, and agentic kit hook wiring. No generic "AI slop" aesthetics.
web3-expert
Build production-ready Web3 applications including smart contracts, dApps, DeFi protocols, and decentralized storage solutions. Use when the user mentions Web3, smart contracts or Solidity, dApps, DeFi protocols, ethers.js or web3.js, IPFS, or on-chain integration with Ethereum-compatible networks.
fintech-expert
Expert in financial technology, payment processing, open banking APIs, PSD2, blockchain in finance, robo-advisors, and RegTech. Use when the user mentions payments, open banking, PSD2, blockchain, cryptocurrency, or robo advisor, or when the task involves Payment Processing, Blockchain in Finance, Payment Security, or…
stellar-mcp
MCP (Model Context Protocol) tools for Stellar development. Gives Claude direct access to the Stellar blockchain, filesystem, GitHub, and Playwright through configured MCP servers. Use when querying chain data, deploying contracts, managing repos, or running e2e tests from within the agent.