agentmods.dev

learn-signals

learn-signals is a skill for Claude Code, Codex from ALTEN-group/coding-pal. It costs 85 tokens per session (591 once invoked), scanned A, original, MIT.

A backlog handoff tool that turns validated incidents, rejected outcome hypotheses, and serious telemetry findings into triage issues. Triage is the process of reviewing and prioritising incoming work.

In plain words
What is it for?
Use it after incident reviews, outcome reviews, or telemetry scans to create and find the corresponding triage issues.
Why use it?
It makes sure lessons and warning signs become trackable backlog work instead of ending in a report that nobody follows up.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths.

not rated 5repo 5d ago A scan 85 tokens original MIT

Good fit Use it after incident reviews, outcome reviews, or telemetry scans to create and find the corresponding triage issues.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alten-group/coding-pal/learn-signals
View source ↗ ALTEN-group/coding-pal alten-group.github.io
Install

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.

Any agent
npx skills add ALTEN-group/coding-pal --skill learn-signals
Clone the repo
git clone --depth 1 https://github.com/ALTEN-group/coding-pal

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for learn-signals

README.md
[![agentmods](https://agentmods.dev/badge/skills/alten-group/coding-pal/learn-signals/github.svg)](https://agentmods.dev/skills/alten-group/coding-pal/learn-signals)
Your own site
<a href="https://agentmods.dev/skills/alten-group/coding-pal/learn-signals"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/learn-signals/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.

agentmods 80×15 button for learn-signals

Your own site · 80×15
<a href="https://agentmods.dev/skills/alten-group/coding-pal/learn-signals"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/learn-signals.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 591 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00085 $0.00591
Opus 5.5 $0.00034 $0.00236
Sonnet 5.5 $0.00017 $0.00118
Haiku 4.5 $0.00009 $0.00059

Measured 4d ago against content hash 6d3a36de8fad, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

learn-signals 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.

The scan reads SKILL.md. This mod also ships 7 executable files (scripts/emit-learn-issues.mjs, scripts/emit-learn-issues.test.mjs, scripts/signals-fixture.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/learn-signals/SKILL.md · 45 lines

How it starts

The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Learn Signals

The Learn stage is finished when a Learn output has become a backlog issue in Triage. This skill emits those issues from inputs that already passed their own validators.

When to Use This Skill

  • An incident record is validated and its Control Hardening items must become backlog issues.
  • The Outcome review invalidated a hypothesis and the feature must be deleted.
  • A telemetry scan produced high findings.
  • The weekly review wants every Learn output that still has no Triage issue.

Path resolution

Resolve references/ and scripts/ relative to this skill's install directory (the folder that contains this SKILL.md), not the consumer repository root or the current shell cwd. If the skill was installed under .agents/skills/learn-signals/ or .claude/skills/learn-signals/, use that base path.

Workflow

  1. Read references/learn-signals-contract.md now. It defines what becomes an issue, the marker, and the body format.
  2. Make sure every input is valid first (incident-record, hypothesis-ledger, telemetry-scan --json). The emitter validates again and refuses to emit from an invalid input.
  3. Emit from this skill's directory:
node scripts/emit-learn-issues.mjs --out learn-signals \
  --incident docs/incidents/2026-10-13-checkout-5xx.md \
  --ledger specs/learn/hypotheses.md \
  --findings findings.json
  1. Report the issues from signals.json (title, marker, labels). In CI, create an issue from each bodyFile with its labels only when no issue with the same marker exists. Do not overwrite or edit existing issues.
  2. Put the new issue number in the incident record's Triage Issue field through a pull request.

Treat a nonzero exit as invalid input and fix the source file. The script is the enforcement gate.

Done When

  • The emitter exited 0 and signals.json lists every control hardening item, deletion, and high finding of the inputs.
  • Each issue carries the labels needs:triage and source:learn and its learn-signal marker.
  • No issue was decided, prioritised, or scored by AI.

Read the full file on GitHub · 45 lines

Files

What ships with it

8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 4d ago First seen · 45 lines · 85 tokens per session scan A 6d3a36de8fad

Subscribe to this mod's changes

learn-signals is a skill published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 5d ago), licensed MIT. It adds 85 tokens to every session and 591 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-10-14.

DebuggingProject management
Related

Other skills, from other repositories

bug-triage

Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.

Donchitos/Claude-Code-Game-Studios · 30 tokens

systemic-issue-triage

Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.

Gentleman-Programming/gentle-ai · 57 tokens

triage-issue-reports

Triage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation. Use only from the configured Benny triage automation.

backnotprop/pstack · 46 tokens

triage-issue

Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…

atlassian/atlassian-mcp-server · 116 tokens

moai-lane-watchdog

One lane stall watchdog iteration: measure lane progress on three channels, classify the stall cause, apply the remedy or resolve the judgment through the decision ladder — instead of waiting on a reply — then record the outcome and report. Reads the unified --auto doctrine at…

modu-ai/moai-adk · 86 tokens

investigation

Create an investigation ticket + live-doc for sustained root-cause work (retros, bug archaeology, regression hunts).

me2resh/apexyard · 26 tokens