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 javiarmesto/ALDC-AL-Development-Collection --skill skill-contribution-assistantgit clone --depth 1 https://github.com/javiarmesto/ALDC-AL-Development-CollectionWrote 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/javiarmesto/aldc-al-development-collection/skill-contribution-assistant)<a href="https://agentmods.dev/skills/javiarmesto/aldc-al-development-collection/skill-contribution-assistant"><img src="https://agentmods.dev/badge/skills/javiarmesto/aldc-al-development-collection/skill-contribution-assistant/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/javiarmesto/aldc-al-development-collection/skill-contribution-assistant"><img src="https://agentmods.dev/badge/skills/javiarmesto/aldc-al-development-collection/skill-contribution-assistant.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00073 | $0.01052 |
| Opus 5 | $0.00036 | $0.00526 |
| Sonnet 5 | $0.00015 | $0.00210 |
| Haiku 4.5 | $0.00007 | $0.00105 |
Grade A, and why
skill-contribution-assistant 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 12d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Central Skill Authoring Playbook
This skill helps contributors move from idea to PR-ready skill with consistent quality standards.
Core Outcomes
- Define a focused and reusable skill scope.
- Avoid intrusive behavior while detecting candidate community skills.
- Apply repository conventions for structure, language, and maintainability.
- Produce a PR-ready package: skill files + release plan entry.
Non-Intrusive Opportunity Detection
This skill can detect when a user request may become a reusable community skill, but must be subtle and optional.
Detection Rules
Trigger detection only when at least 3 conditions are true:
- Problem appears repeatable across projects or teams.
- Solution requires multi-step workflow, not a single code snippet.
- Stable inputs/outputs can be documented.
- The request can be generalized without customer-specific data.
- The expected value is broader than one ticket.
Intrusion Guardrails
- Suggest at most once per topic.
- Use one short prompt only.
- If user says no, stop suggesting in the current conversation.
- Never block the original task.
Suggestion Pattern
Use this exact style:
Potential community skill candidate detected: this workflow looks repeatable and reusable. Would you like to convert it into a skill proposal now?
If user declines, continue normally. If user accepts, run onboarding interview.
Mandatory Onboarding (After User Says Yes)
Once the user confirms they want to build the skill, ask these questions before drafting content.
- What exact problem does the skill solve?
- Who is the primary user of this skill?
- What should trigger the skill? (phrases, contexts, intents)
- Which tasks are in scope?
- Which tasks are out of scope?
- Is terminal execution required? If yes, which commands/tools?
- Should the skill guide only, or also execute tasks automatically?
- Which artifacts are expected? (files, scripts, checklists, templates)
- Are there privacy/security constraints? (IPs, customers, credentials, internal paths)
- What is the Definition of Done for this skill?
What ships with it
4 files 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.
- 12d ago First seen · 136 lines · 73 tokens per session scan A 541ba11eee93
skill-contribution-assistant is a skill published in the GitHub repository javiarmesto/ALDC-AL-Development-Collection (104 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 1,052 once invoked, about $0.0004 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
android-data-persistence
Use when implementing local data storage with Room, DataStore, or offline-first patterns. Covers entities, DAOs, migrations, Paging3, and the repository pattern for data management.
android-device-testing
Use when writing or debugging instrumented tests (Espresso, UI Automator, Compose test rules), using ADB, managing emulators, or inspecting UI with Layout Inspector.
ci-cd-and-automation
Use when setting up or improving CI/CD pipelines for Android. Covers sequential quality gates, Gradle caching, emulator testing in CI, feature flags, and automated deployment to Play Store.
security-and-hardening
Use when handling sensitive data, authentication, network communication, or before shipping to the Play Store. Three-tier framework (Always Do, Ask First, Never Do) with Android-specific security patterns.
api-and-interface-design
Use when designing interfaces between layers (Repository, UseCase, API client) or defining data contracts. Covers Retrofit interfaces, Room DAOs, Kotlin sealed classes, and backward compatibility.
deprecation-and-migration
Use when deprecating APIs, bumping minSdk, migrating libraries (AndroidX, Compose, Kotlin versions), or removing legacy code. Covers Kotlin @Deprecated annotation, strangler pattern, and incremental migration.