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 ashfulcra/fulcra-tools --skill fulcra-csvgit clone --depth 1 https://github.com/ashfulcra/fulcra-toolsWrote 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/ashfulcra/fulcra-tools/fulcra-csv)<a href="https://agentmods.dev/skills/ashfulcra/fulcra-tools/fulcra-csv"><img src="https://agentmods.dev/badge/skills/ashfulcra/fulcra-tools/fulcra-csv/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/ashfulcra/fulcra-tools/fulcra-csv"><img src="https://agentmods.dev/badge/skills/ashfulcra/fulcra-tools/fulcra-csv.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 375 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Data Exfiltration · line 27 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00071 | $0.05114 |
| Opus 5 | $0.00036 | $0.02557 |
| Sonnet 5 | $0.00014 | $0.01023 |
| Haiku 4.5 | $0.00007 | $0.00511 |
Grade A, and why
fulcra-csv scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Target picked + def exists? | for a user-defined/generic annotation, list the account's live annotation definitions and confirm the intended UUID is present: `curl --oauth2-bearer "$(fulcra auth print-access-token)" ht How it starts
The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fulcra-csv — Import any CSV into Fulcra
fulcra-csv is a small CLI that maps CSV columns onto Fulcra annotation events. It's the foundation fulcra-media-helpers uses for its generic-csv importer, but it works standalone for any kind of data: weights, moods, expenses, water intake, custom logs.
This skill teaches you (the AI agent) how to import a CSV into the right Fulcra annotation type for a given user data shape.
Where to start — the re-entrancy probes
Before running an import, probe how far this user already got. The states are a prefix of
the import flow — authed? → target def exists? → anything-to-import? → already landed? — so
enter at the first probe that fails (per the repo's skill-quality pattern,
docs/skill-quality-pattern.md). Every state is safely re-enterable: re-running an import produces
the same deterministic source_ids, and the importer dedups against a readback of existing source_ids
before posting (client-side, in run_import; see "Critical invariant" below), so there is never a
penalty for re-probing or re-importing.
| Probe (run in order) | Command | Passes when | If it fails, enter at |
|---|---|---|---|
| Authed? | fulcra auth print-access-token |
exits 0 and prints a non-empty token (the CLI mints/refreshes it; FULCRA_ACCESS_TOKEN in the env also satisfies this) |
AUTH — tell the user to run fulcra auth login (interactive browser flow); see "Fulcra Life API auth" below |
| Target picked + def exists? | for a user-defined/generic annotation, list the account's live annotation definitions and confirm the intended UUID is present: curl --oauth2-bearer "$(fulcra auth print-access-token)" https://api.fulcradynamics.com/user/v1alpha1/annotation (this is the GET annotations_catalog() reads; fulcra catalog lists data types, not user-defined annotation defs, so don't use it here). For a built-in type (--data-type BodyMass, etc.), no def is needed — this probe is N/A |
the intended --definition-id UUID appears in the JSON with deleted_at null, OR the user is targeting a built-in type |
BOOTSTRAP — mint a def with fulcra-csv bootstrap … (prints the UUID), then import against it. Do NOT bootstrap if the UUID is already present — that mints a duplicate def and splits the data |
| Anything to import? | fulcra-csv import <csv-path> --dry-run with a target flag — --definition-id <uuid> (user-defined) or --data-type <Name> (built-in), plus the same column flags you'll use for the real run. --dry-run skips auth/ingest but the CLI still rejects the run with a UsageError if neither --definition-id nor --data-type is present (there'd be no target), so pass one even in dry-run |
prints parsed N events … with N > 0 and the sampled rows look right (pure parse — no auth or ingest) |
EXPORT/COLLECT — the file is empty or the column mapping is wrong; fix the flags or get a better file before importing |
| Already landed? | fulcra-csv export --definition-id <uuid> --start "30 days ago" --columns start_time,source_id (built-in target: pass --data-type <Name> instead) |
rows come back that match the CSV you're about to import (compare source_id hashes or timestamps) |
IMPORT — nothing landed yet; run fulcra-csv import … for real (drop --dry-run) |
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 · 376 lines · 71 tokens per session scan A 23ee795e5889
fulcra-csv is a skill published in the GitHub repository ashfulcra/fulcra-tools (10 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 5,114 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
magic-compact
Compact this Claude Code session.
citation-intelligence
Use when the user wants to know which URLs AI engines cite for a query, whether their domain is being cited by ChatGPT/Claude/Perplexity/Gemini/Google AI Overviews/Bing, what queries their site is cited for, how citation rate changes over time, or how their citation coverage compares to competitors. Self-hosted, BYO…
proof-engine
Create formal, verifiable proofs of claims with machine-checkable reasoning. Use when asked to prove, verify, fact-check, or rigorously establish whether a claim is true or false — mathematical, empirical, or mixed. Trigger phrases: "is it really true", "can you prove", "verify this", "fact-check this", "prove it"…
join
Join the Cortex agent team — reads agent config from team directory, generates .cortex.md protocol, updates CLAUDE.local.md. Idempotent — safe to re-run as a sync.
setup
First-time Cortex setup — creates team directory, config, and chief of staff agent.
leave
Leave the Cortex agent team — removes .cortex.md, cleans CLAUDE.local.md, sets agent status to inactive in team directory.