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 agentmods add skills/plurigrid/asi/abductive-replnpx skills add plurigrid/asi --skill abductive-replgit clone --depth 1 https://github.com/plurigrid/asiWrote 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/plurigrid/asi/abductive-repl)<a href="https://agentmods.dev/skills/plurigrid/asi/abductive-repl"><img src="https://agentmods.dev/badge/skills/plurigrid/asi/abductive-repl.svg" alt="Measured on agentmods" 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.00027 | $0.01034 |
| Opus 5 | $0.00014 | $0.00517 |
| Sonnet 5 | $0.00005 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
abductive-repl 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
abductive-repl
Hypothesis-Test Loops via REPL for Exploratory Abductive Inference
Version: 1.1.0 (music-topos enhanced) Trit: 0 (Ergodic - coordinates inference) Bundle: repl
Overview
Abductive-REPL enables exploratory abductive reasoning through an interactive REPL. Given observed outcomes, it generates hypotheses, tests them, and refines understanding through iterative loops.
Core Concept
Observation → Generate Hypotheses → Test → Refine → Repeat
Abduction: Given effect E and rule "A implies E",
hypothesize A as possible cause.
Enhanced Integration: Interpreters
Julia (Gay.jl) - Primary
# Start abductive REPL with Gay.jl
julia --project=Gay.jl -e 'using Gay; Gay.repl()'
# In REPL:
gay> !abduce 216 125 157
# Searches invader space for color match
Hy (HyJAX) - Secondary
;; thread_relational_hyjax.hy integration
(import lib.thread_relational_hyjax :as tra)
(defn abduce-from-color [r g b]
"Abduce invader ID from observed RGB"
(let [target [r g b]
analyzer (tra.ThreadRelationalAnalyzer)]
;; Search hypothesis space
(lfor id (range 1 10000)
:if (color-match? id target 0.05)
{:hypothesis id :confidence (- 1.0 (color-distance id target))})))
Babashka (bb) - Scripting
;; abductive_repl.bb
(require '[babashka.process :refer [shell]])
(defn abduce [observed-color]
(let [result (shell {:out :string}
"julia" "--project=Gay.jl" "-e"
(format "using Gay; Gay.abduce(RGB(%s))"
(clojure.string/join "," observed-color)))]
(parse-hypotheses (:out result))))
REPL Commands Enhanced
| Command | Description | Interpreter |
|---|---|---|
!teleport <id> |
Jump to invader's world state | Julia |
!abduce r g b |
Infer invader from observed RGB | Julia/Hy |
!test [n] |
Run n abductive roundtrip tests | Julia |
!hy-analyze |
Run HyJAX relational analysis | Hy |
!bb-export |
Export hypotheses via Babashka | Babashka |
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 · 133 lines · 27 tokens per session scan A 3b2fb366bebe
abductive-repl is a skill published in the GitHub repository plurigrid/asi (62 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 1,034 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-01.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…