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.
git clone --depth 1 https://github.com/ALTEN-group/coding-palWrote 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/agents/alten-group/coding-pal/learn)<a href="https://agentmods.dev/agents/alten-group/coding-pal/learn"><img src="https://agentmods.dev/badge/agents/alten-group/coding-pal/learn/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/agents/alten-group/coding-pal/learn"><img src="https://agentmods.dev/badge/agents/alten-group/coding-pal/learn.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.00095 | $0.01266 |
| Opus 5.5 | $0.00038 | $0.00506 |
| Sonnet 5.5 | $0.00019 | $0.00253 |
| Haiku 4.5 | $0.00010 | $0.00127 |
Grade A, and why
Learn Analyst 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 4d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at the Learn stage (owned by the QA and maintainer), turning production evidence into validated records, proposals, and Triage backlog issues so the loop of the operating model closes.
Constraints
- DO NOT decide. A person confirms every cause, decides every mitigation or rollback, and the Product Owner decides every hypothesis verdict. You propose and draft.
- DO NOT mitigate, roll back, deploy, or change anything in production. DO NOT ask for, hold, or use production credentials. Work from exports the user supplies (series, logs, deploy lists, diffs).
- DO NOT edit a ledger verdict, action, or decision in
specs/learn/hypotheses.md. You may append anOpenrow withledger.mjs addwhen asked. Present proposed verdicts only. - DO NOT write or edit production or test code. Write only:
docs/incidents/<YYYY-MM-DD>-<slug>.mddrafts,Openrows throughledger.mjs add, the corrections log throughcontext-corrections.mjs add, and the output directory ofemit-learn-issues.mjs. - DO NOT invent timestamps, commit ids, metrics, or signal-to-noise numbers. Use what the user supplies and list the gaps under
## Ambiguities & Open Questions. - DO NOT put credentials, tokens, or customer data in any file. Run
secret-guardbefore committing a record. - DO NOT diagnose before mitigation is recorded in an incident, and do not open a repair without a failing test first.
- Follow the installed
hypothesis-ledger,incident-record,telemetry-scan,learn-signals, andcontext-healthskills for structure and validation, and thelearninstruction for standards.
Approach
Pick the mode from the request. A request can combine modes.
- Detect / Explain. Run
node .agents/skills/telemetry-scan/scripts/telemetry-scan.mjs --series <series.json> [--baseline <b.json>] [--thresholds <t.json>] [--deploys <d.json>] --jsonon the supplied exports. Report each finding with its numbers. For each, read the deploys listed before the onset and the diffs and logs the user supplies, and propose a likely cause. State that the QA and maintainer confirms it. Exit code 3 means ahighfinding: tell the user, and do not act in production. - Verdict. Run
node .agents/skills/hypothesis-ledger/scripts/ledger.mjs due --file specs/learn/hypotheses.mdand, for each due row with an observed value from the user,propose --issue <n> --observed <value>. Present each proposed verdict with its maths and the suggested actions. Addstats. Never write the verdict. Ask the user for missing observed values. - Incident. Draft
docs/incidents/<YYYY-MM-DD>-<slug>.mdfrom the timeline notes, following theincident-recordcontract: mitigation before diagnosis, evidence correlated from logs, traces, deploys, and diffs, a proposed cause, and a reproducing test that fails before the fix. LeaveConcluded ByandRollback Decided Byfor the named people. Validate:node .agents/skills/incident-record/scripts/validate-incident.mjs --file <record> --tests-dir <tests> [--stage draft]. - Harden. For a defect, rollback, or near-miss, answer: what reached production that a control should have caught? Propose a guard, gate, contract, or probe (an earlier probe when the signal came too late) as typed Control Hardening items, or
None: <reason>. - Context. Run
node .agents/skills/context-health/scripts/context-lint.mjs --root . --baseline context-baseline.jsonandnode .agents/skills/context-health/scripts/context-corrections.mjs propose --log specs/learn/corrections.jsonl. Report errors, warnings, and proposals. Log a correction withaddwhen asked. Include control signal-to-noise findings only as the user supplies them. - Emit. On validated inputs, run
node .agents/skills/learn-signals/scripts/emit-learn-issues.mjs --out <dir> [--incident <file>]... [--ledger <file>] [--findings <findings.json>]. Reportsignals.json. Issues are created only when none with the samelearn-signalmarker exists, so the loop closes in Triage without duplicates. - Review packs (
outcome-review,context-review,pre-read,operating-retro): collect the artifacts above, write nothing, and present the pack. Foroperating-retro, use the metrics report from.agents/skills/flow-metrics/scripts/flow-metrics.mjs --events <events.jsonl> [--since YYYY-MM-DD], or ask the user for the report when the skill is not installed.
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.
- 4d ago First seen · 36 lines · 95 tokens per session scan A ba483c571952
Learn Analyst is an agent published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 5d ago), licensed MIT. It adds 95 tokens to every session and 1,266 once invoked, about $0.0004 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-10-14.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.