Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_Mallnpx agentmods add skills/fabioc-aloha/alex_skill_mall/config-transcription-verificationWrote 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/config-transcription-verification)<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/config-transcription-verification"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/config-transcription-verification/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/config-transcription-verification"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/config-transcription-verification.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.00019 | $0.00631 |
| Opus 5 | $0.00010 | $0.00316 |
| Sonnet 5 | $0.00004 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
config-transcription-verification 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 9d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Config Transcription Verification
The Problem
When extracting hardcoded data to JSON, field values silently drift:
// Original code
const buttons = [
{ icon: 'play', label: 'Start', action: 'start' },
{ icon: 'stop', label: 'Stop', action: 'stop' }
];
// Transcribed JSON (with typos)
{
"buttons": [
{ "icon": "play", "label": "Start", "action": "begin" },
{ "icon": "pause", "label": "Stop", "action": "stop" }
]
}
Two errors: action: "begin" instead of "start", icon: "pause" instead of "stop".
The Solution
Cross-check every field against the source.
Manual Verification Checklist
## Transcription Verification
Source: `src/buttons.js` lines 12-18
| Field | Original | JSON | ✓ |
|-------|----------|------|---|
| button[0].icon | play | play | ✅ |
| button[0].label | Start | Start | ✅ |
| button[0].action | start | start | ✅ |
| button[1].icon | stop | stop | ✅ |
| button[1].label | Stop | Stop | ✅ |
| button[1].action | stop | stop | ✅ |
Automated Verification Script
// scripts/verify-transcription.cjs
const source = require('../src/buttons.js').buttons;
const transcribed = require('../config/buttons.json').buttons;
source.forEach((srcItem, i) => {
const jsonItem = transcribed[i];
Object.keys(srcItem).forEach(key => {
if (srcItem[key] !== jsonItem[key]) {
console.error(`Mismatch at [${i}].${key}: "${srcItem[key]}" vs "${jsonItem[key]}"`);
process.exitCode = 1;
}
});
});
if (!process.exitCode) console.log('Transcription verified ✓');
High-Risk Fields
| Field Type | Risk | Verification |
|---|---|---|
| Icon names | High — typos render wrong icon | Visual check |
| Action strings | High — breaks functionality | Unit test |
| Labels | Medium — visible to users | Spell check |
| IDs | High — breaks references | Grep for usage |
Verification
- Every field in original has matching field in JSON
- No extra fields added
- Order preserved where it matters
- Verification script passes
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.
- 9d ago First seen · 100 lines · 19 tokens per session scan A 7c7e5bc49274
config-transcription-verification is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 631 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
qa
Systematic QA testing of a web application: diff-aware, tiered, with fix-and-verify loop.
generate-tests
Generate comprehensive tests for specified code.
code-qualities-assessment
Assess code maintainability through 5 foundational qualities (cohesion, coupling, encapsulation, testability, non-redundancy) with quantifiable scoring rubrics. Works at method/class/module levels across multiple languages. Produces markdown reports with remediation guidance. Use when you ask to "assess…
pr-quality-qa
Judge a local diff on test coverage, error handling, and whether the tests would fail if the code regressed, and return a PASS/WARN/CRITICALFAIL verdict. Use when you say qa review my changes, run the qa gate, or are these tests good enough. Do NOT use to run all six axes (use pr-quality-all), and do NOT use to write…
api-integration-test
Create, maintain, and run gated Go integration tests for internal APIs and service-to-service clients (HTTP/gRPC). Use for endpoint verification, contract checks with real runtime config, opt-in execution, timeout/retry safety, and integration failure triage in Go services.
go-test-review
Review Go test code for quality including table-driven tests, t.Helper usage, assertion completeness, boundary cases, benchmarks, fuzz tests, and coverage targets. Trigger when PR contains test.go files, test helpers, httptest usage, testing.B, testing.F, or testdata directories. Use for test-quality focused review.