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 heristop/leclap --skill core-architecture-patternsgit clone --depth 1 https://github.com/heristop/leclapWrote 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/heristop/leclap/core-architecture-patterns)<a href="https://agentmods.dev/skills/heristop/leclap/core-architecture-patterns"><img src="https://agentmods.dev/badge/skills/heristop/leclap/core-architecture-patterns/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/heristop/leclap/core-architecture-patterns"><img src="https://agentmods.dev/badge/skills/heristop/leclap/core-architecture-patterns.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.00064 | $0.01955 |
| Opus 5.5 | $0.00026 | $0.00782 |
| Sonnet 5.5 | $0.00013 | $0.00391 |
| Haiku 4.5 | $0.00006 | $0.00196 |
Grade A, and why
core-architecture-patterns 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 24d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Architecture Patterns
Overview
packages/ffmpeg-video-composer is built from a few repeating patterns: adapters abstract the platform, the PlatformBridge selects them for Node while browser/native entry points register them directly, tsyringe DI wires everything, and a director → builder → segments → managers pipeline compiles a template. Follow these patterns; reuse existing pieces before adding new ones. Full design: docs/architecture.md.
The pipeline
TemplateDirector (packages/ffmpeg-video-composer/src/director/TemplateDirector.ts) orchestrates:
init → build each section → concat → apply music.
- Sections created by
SegmentFactory(editor/factories/SegmentFactory.ts) → rendered by*Segmentclasses (editor/segments/). - FFmpeg commands assembled by editor managers (
editor/managers/): asset, variable, map, filter, formatter. VideoEditorconcatenates;MusicComposermixes audio.
Adding a segment type
- Add the section schema variant in
packages/ffmpeg-video-composer/src/schemas/section.schemas.ts(extendBaseSectionSchema, add to theSectionSchemadiscriminated union);template.schemas.tsre-exports it. Keep the manual descriptor shape insrc/core/types.d.tsin sync. - Create
editor/segments/<Name>Segment.tsfollowing an existing segment (e.g.VideoSegment.ts); use@injectable(). - Register it in
editor/factories/SegmentFactory.ts(map the newtypeliteral → class). - Add a test under
packages/ffmpeg-video-composer/tests/.
An authoring effect section follows a different route: EffectReferenceSchema in schemas/effect-reference.schema.ts defines its JSON contract, and core/resolve-template-effects.ts resolves it into a project_video clip plus userVideoPaths before compilation. The core never launches Remotion. Extend the trusted Node backend/catalog in packages/leclap-mcp/src/effects/ for registered graphics, validate props/assets during preflight, and expose contracts through get_effect_schema; do not add a Remotion segment to SegmentFactory.
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.
- 24d ago Changed · +2 lines · +6 tokens per session 36a8c6d269a5
- 1mo ago First seen · 75 lines · 58 tokens per session scan A 178295ed2811
core-architecture-patterns is a skill published in the GitHub repository heristop/leclap (36 stars, last pushed 4d ago), licensed MIT. It adds 64 tokens to every session and 1,955 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
qiaomu-cut
A workflow for turning a brief video idea into a planned, sourced, edited, rendered, and checked video project.
push-notifications
Set up push notifications for iOS and Android using Expo Notifications and Supabase Edge Functions. Use when adding push notifications, configuring APNs/FCM credentials, sending notifications from the backend, or troubleshooting notification delivery.
social-auth-setup
Configure Sign in with Apple and Sign in with Google for Supabase Auth. Use when adding social login, troubleshooting OAuth redirects, setting up Apple Services ID, Google OAuth credentials, or linking Google Play Console to Google Cloud.
supabase-email-templates
Customize Supabase Auth email templates for local development and production.
edge-functions
Supabase Edge Function development patterns with Deno runtime. Use when creating, modifying, or debugging edge functions. For Langfuse tracing see the langfuse-tracing skill. For Sentry error handling see the sentry-integration skill.
nestjs
Use when building or structuring a NestJS backend — feature modules, providers and DI wiring, provider scopes and request-lifecycle order, where to bind guards/pipes/interceptors/filters, and testing with Test.createTestingModule. NOT a bare Express/Fastify service with no DI (that is nodejs), NOT framework-agnostic…