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 conductgit 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/conduct)<a href="https://agentmods.dev/skills/javiarmesto/aldc-al-development-collection/conduct"><img src="https://agentmods.dev/badge/skills/javiarmesto/aldc-al-development-collection/conduct/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/conduct"><img src="https://agentmods.dev/badge/skills/javiarmesto/aldc-al-development-collection/conduct.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.00353 |
| Opus 5.5 | $0.00021 | $0.00141 |
| Sonnet 5.5 | $0.00011 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
conduct 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 today.
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
/aldc:conduct
Read ${CLAUDE_PROJECT_DIR}/claude-plugin/agents/al-conductor.md in full and act as that agent for the rest of this session; the Copilot-to-Claude Code mappings and the Claude Code runtime rules at the top of that file are binding. You stay the orchestrator in this main session because only the main session can launch subagents. Orchestrating means delegating: research goes to aldc:al-planning-subagent, each phase to aldc:al-implement-subagent and each review to aldc:al-review-subagent, through the Agent/Task tool, in the foreground. Never do that work yourself, even when the task looks small. If the host does not let you launch subagents, say so and stop; do not simulate the subagents. For an enforced tool list, launch claude --agent aldc:al-conductor instead.
Input: $ARGUMENTS
Requirement artifacts live under .claude/plans/ in the project; run /aldc:al-initialize once if that folder does not exist.
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.
- today Changed b10ca469ad4b
- 26d ago Changed fa3505fecfbd
- 1mo ago First seen · 16 lines · 53 tokens per session scan A 32c896ca136a
conduct is a skill published in the GitHub repository javiarmesto/ALDC-AL-Development-Collection (109 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 353 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-09-19.
Other skills, from other repositories
test-driven-development
Use when implementing new features or fixing bugs. Write tests before implementation following Red-Green-Refactor. Covers JUnit5, MockK, Compose test rules, and the Prove-It pattern for bugs.
test-strategy
Produces a test strategy document defining what to test, at which layer, with which tools, and to what coverage standard. It applies the test pyramid model, surfaces coverage gaps in existing codebases, and produces a concrete plan — not a generic "write more tests" recommendation.
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
test-driven-development
Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.
tdd-enforcement
Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.