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 fabioc-aloha/Alex_Skill_Mall --skill staged-transformation-pipelinegit clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_MallWrote 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/fabioc-aloha/alex_skill_mall/staged-transformation-pipeline)<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/staged-transformation-pipeline"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/staged-transformation-pipeline/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/fabioc-aloha/alex_skill_mall/staged-transformation-pipeline"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/staged-transformation-pipeline.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.00017 | $0.00650 |
| Opus 5 | $0.00009 | $0.00325 |
| Sonnet 5 | $0.00003 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
staged-transformation-pipeline 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 8d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Staged Transformation Pipeline
The Problem
Monolithic transformations are hard to test and debug:
// Bad: everything in one function
function processInput(input) {
// 200 lines of parsing, validation, transformation, formatting
return output;
}
When something breaks, you don't know which stage failed.
The Solution
Input flows through discrete stages. Each stage is independently testable.
// Define stages
const stages = {
parse: (input) => JSON.parse(input),
validate: (data) => {
if (!data.id) throw new Error('Missing id');
return data;
},
transform: (data) => ({
...data,
processedAt: new Date().toISOString()
}),
format: (data) => JSON.stringify(data, null, 2)
};
// Pipeline runner
function runPipeline(input, stageOrder = ['parse', 'validate', 'transform', 'format']) {
let result = input;
for (const stageName of stageOrder) {
try {
result = stages[stageName](result);
} catch (err) {
throw new Error(`Pipeline failed at stage '${stageName}': ${err.message}`);
}
}
return result;
}
Benefits
1. Independent Testing
// Test each stage in isolation
describe('validate stage', () => {
it('rejects missing id', () => {
expect(() => stages.validate({})).toThrow('Missing id');
});
it('passes valid data through', () => {
expect(stages.validate({ id: 1 })).toEqual({ id: 1 });
});
});
2. Stage Replacement
// Swap out a stage without touching others
stages.format = (data) => yaml.dump(data); // Now outputs YAML
3. Debugging
// Log between stages
function debugPipeline(input, stageOrder) {
let result = input;
for (const stageName of stageOrder) {
console.log(`[${stageName}] Input:`, result);
result = stages[stageName](result);
console.log(`[${stageName}] Output:`, result);
}
return result;
}
Stage Design Rules
- Pure functions — no side effects within stages
- Single responsibility — one transformation per stage
- Typed contracts — each stage has clear input/output types
- Fail fast — validate early, don't propagate bad data
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.
- 8d ago First seen · 119 lines · 17 tokens per session scan A a9cbab99e160
staged-transformation-pipeline is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 650 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
flutter-bloc-state-management
Implement BLoC/Cubit state, events, transitions, and async concurrency in Flutter. Use for BLoC/Cubit feature logic, debounced/cancellable events, state rendering, or bloc tests—not generic widget-only work.
qa
Systematic QA testing of a web application: diff-aware, tiered, with fix-and-verify loop.
unit-test
A Go testing workflow for writing unit tests: small tests that check individual functions or components. It supports table-driven cases, where many inputs and expected results are organised in one test, and subtests.
fuzzing-test
A Go testing guide for generating fuzz tests, which repeatedly try varied inputs to find crashes and unexpected behavior. It first checks whether the code is suitable for fuzzing.
debugging
Use when debugging bugs, test failures, or unexpected behavior. Triggers: 'why isn't this working', 'this doesn't work', 'X is broken', 'something's wrong', 'getting an error', 'exception in', 'stopped working', 'regression', 'crash', 'hang', 'flaky test', 'intermittent failure', or when user pastes a stack…
analyze-failures
Triage Katalon True Platform/TestOps test failures and file defects. Use when you need to investigate failed test results, classify each failure as product defect vs automation defect vs environment/data issue, cluster failures by common signature, find likely root cause from execution data, and optionally create…