Borrowing it
Nothing to install: this file belongs to byaan-ai/byaan. 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/byaan-ai/byaan/main/.agents/skills/byaan:learn/SKILL.mdgit clone --depth 1 https://github.com/byaan-ai/byaanWrote 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/byaan-ai/byaan/byaan-learn)<a href="https://agentmods.dev/skills/byaan-ai/byaan/byaan-learn"><img src="https://agentmods.dev/badge/skills/byaan-ai/byaan/byaan-learn/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/byaan-ai/byaan/byaan-learn"><img src="https://agentmods.dev/badge/skills/byaan-ai/byaan/byaan-learn.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium Agent Snooping · line 53 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 140 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00046 | $0.01371 |
| Opus 5 | $0.00023 | $0.00685 |
| Sonnet 5 | $0.00009 | $0.00274 |
| Haiku 4.5 | $0.00005 | $0.00137 |
Grade A, and why
byaan:learn 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 13d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a codebase analyst. Your job is to deeply analyze this project's data layer and build (or update) a skill that teaches AI how to write accurate queries against the databases in this codebase.
This skill can be run at any time to learn or re-learn the codebase. It is also invoked automatically during /byaan:start onboarding.
Step 1: Deep Codebase Analysis
Analyze the following in order. Be exhaustive. Read every relevant file.
Database Models & Schema
- Find ALL model/schema definition files (SQLAlchemy, Mongoose, Prisma, Sequelize, TypeORM, Django models, Drizzle, etc.)
- For each model/collection, document:
- Table/collection name (actual DB name, not class name)
- Every field: name, type, nullable, defaults, constraints
- Primary keys, foreign keys, unique constraints
- Indexes (single, compound, unique, partial, text)
- Relationships (one-to-one, one-to-many, many-to-many) with join tables/foreign keys
- Enums and their possible values
- Soft deletes, timestamps, versioning patterns
Data Access Patterns
- Find ALL places models are queried: repositories, DAOs, services, controllers, scripts, migrations, seeders, jobs, workers
- For each, document:
- What queries are commonly run (CRUD, aggregations, joins, subqueries)
- Filtering patterns (common WHERE clauses, date ranges, status filters)
- Pagination approaches (offset, cursor, keyset)
- Sorting conventions
- Aggregation pipelines (MongoDB) or GROUP BY patterns (SQL)
- Raw queries vs ORM usage
- Transaction patterns
- Bulk operations
Business Domain Context
- What do the entities represent in business terms?
- What are the core domain relationships? (e.g., "A User has many Notebooks, each Notebook has many Queries")
- What are the most important entities and why?
- What status flows exist?
- What are the tenant/org/workspace scoping rules?
Query Performance & Conventions
- What indexes exist and what queries do they optimize?
- Are there materialized views, CTEs, or complex SQL patterns?
- MongoDB: aggregation pipelines? Change streams? Atlas Search?
- Naming conventions (snake_case, camelCase, plural table names, etc.)
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.
- 13d ago First seen · 143 lines · 46 tokens per session scan A 1b54c06d8076
byaan:learn is a skill published in the GitHub repository byaan-ai/byaan (95 stars, last pushed 17d ago), licensed MIT. It adds 46 tokens to every session and 1,371 once invoked, about $0.0002 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-30.
Other skills, from other repositories
chroma
Open-source embedding database for AI applications. Store embeddings and metadata, perform vector and full-text search, filter by metadata. Simple 4-function API. Scales from notebooks to production clusters. Use for semantic search, RAG applications, or document retrieval. Best for local development and open-source…
effective-dbt-sql
Use when writing or modifying dbt model SQL — deciding whether to add a subquery or reuse an existing dimension/metric, structuring a query, joining models, or refactoring a metric's SQL. Encodes SQL semantic-correctness rules: reuse existing fields, prefer CTEs over correlated subqueries, and make joins and column…
chroma
Open-source embedding database for AI applications. Store embeddings and metadata, perform vector and full-text search, filter by metadata. Simple 4-function API. Scales from notebooks to production clusters. Use for semantic search, RAG applications, or document retrieval. Best for local development and open-source…
data_modeling_standards
Reference guide for business rules, naming conventions, and data modeling standards enforced during data product development.
chroma
Open-source embedding database for AI applications. Store embeddings and metadata, perform vector and full-text search, filter by metadata. Simple 4-function API. Scales from notebooks to production clusters. Use for semantic search, RAG applications, or document retrieval. Best for local development and open-source…
chroma
Open-source embedding database for AI applications. Store embeddings and metadata, perform vector and full-text search, filter by metadata. Simple 4-function API. Scales from notebooks to production clusters. Use for semantic search, RAG applications, or document retrieval. Best for local development and open-source…