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 eddiebelaval/squire --skill entity-extractorgit clone --depth 1 https://github.com/eddiebelaval/squireWrote 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/eddiebelaval/squire/entity-extractor)<a href="https://agentmods.dev/skills/eddiebelaval/squire/entity-extractor"><img src="https://agentmods.dev/badge/skills/eddiebelaval/squire/entity-extractor.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.00014 | $0.02427 |
| Opus 5 | $0.00007 | $0.01213 |
| Sonnet 5 | $0.00003 | $0.00485 |
| Haiku 4.5 | $0.00001 | $0.00243 |
Grade A, and why
Entity Extractor 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 3d 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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Entity Extractor
The Entity Extractor skill guides you through implementing named entity recognition (NER) systems that identify and classify entities in text. From people and organizations to domain-specific entities like products, medical terms, or financial instruments, this skill covers extraction approaches from simple pattern matching to advanced neural models.
Entity extraction is a foundational NLP task that powers applications from search engines to knowledge graphs. Getting it right requires understanding your domain, choosing appropriate techniques, and handling the inherent ambiguity in natural language.
Whether you need to extract standard entity types, define custom entities for your domain, or build relation extraction on top of entity recognition, this skill ensures your extraction pipeline is accurate and maintainable.
Core Workflows
Workflow 1: Choose Extraction Approach
- Define target entities:
- Standard types: PERSON, ORG, LOCATION, DATE, MONEY
- Domain-specific: PRODUCT, SYMPTOM, GENE, CONTRACT
- Relations: connections between entities
- Assess available resources:
- Labeled training data
- Domain expertise
- Compute constraints
- Select approach:
Approach Training Data Accuracy Speed Customization spaCy (pre-trained) None Good Very fast Limited Rule-based None Variable Fast High Fine-tuned BERT 100s-1000s Excellent Medium Full LLM (zero-shot) None Good Slow Prompt-based LLM (few-shot) Few examples Very good Slow Prompt-based - Plan implementation and evaluation
Workflow 2: Implement Entity Extraction Pipeline
- Set up extraction:
import spacy class EntityExtractor: def __init__(self, model="en_core_web_trf"): self.nlp = spacy.load(model) def extract(self, text): doc = self.nlp(text) entities = [] for ent in doc.ents: entities.append({ "text": ent.text, "type": ent.label_, "start": ent.start_char, "end": ent.end_char, "confidence": getattr(ent, "confidence", None) }) return entities def extract_batch(self, texts): docs = list(self.nlp.pipe(texts)) return [self.extract_from_doc(doc) for doc in docs] - Post-process entities:
- Normalize variations (IBM vs I.B.M.)
- Resolve abbreviations
- Link to knowledge base
- Validate extraction quality
- Handle edge cases
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.
- 3d ago First seen · 341 lines · 14 tokens per session scan A 0584381e63cf
Entity Extractor is a skill published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 21d ago), licensed MIT. It adds 14 tokens to every session and 2,427 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
Entity Extractor
Extract named entities from text with high accuracy and customization.
nlp
Use when choosing how to tokenize text or which transformer type fits an NLP task, when a tokenizer over-fragments non-English text or inflates token cost, when picking a language metric, or when classification, NER or summarization output looks wrong and it is unclear whether the tokenizer, the architecture or the…
Embedding Generator
Generate and manage text embeddings for semantic search, clustering, and similarity tasks.
flow-nexus-neural
Train and deploy neural networks in distributed E2B sandboxes with Flow Nexus.
transformers
This skill should be used when working with pre-trained transformer models for natural language processing, computer vision, audio, or multimodal tasks. Use for text generation, classification, question answering, translation, summarization, image classification, object detection, speech recognition, and fine-tuning…
golden-dataset
Golden dataset lifecycle patterns for curation, versioning, quality validation, and CI integration. Use when building evaluation datasets, managing dataset versions, validating quality scores, or integrating golden tests into pipelines.