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 1A7432/loreweaver --skill romance-relationshipsgit clone --depth 1 https://github.com/1A7432/loreweaverWrote 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/1a7432/loreweaver/romance-relationships)<a href="https://agentmods.dev/skills/1a7432/loreweaver/romance-relationships"><img src="https://agentmods.dev/badge/skills/1a7432/loreweaver/romance-relationships.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.00595 |
| Opus 5 | $0.00020 | $0.00298 |
| Sonnet 5 | $0.00008 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
Romance & relationships 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 8d 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.
What it actually says
Romance & relationships
This table is playing a relationship-forward campaign: romance, courtship, and intimacy are a load-bearing part of the story, not a side quest. Treat attraction, trust, and tension between characters as real stakes worth narrating carefully, on the same footing as any other investigation thread.
Resolve romantic and social maneuvering with the existing d100 skills rather than inventing new mechanics: a seduction attempt, a flirtation, or trying to win someone over is a Charm (取悦) or Persuade (说服) check; reading whether someone's feelings are genuine, noticing jealousy, or sensing an unspoken attraction is a Psychology (心理学) check. Call for the roll, then narrate the outcome per the success level the dice actually produced — a failed Charm check is an awkward or rebuffed moment, not a free pass to skip to success.
This table has deterministic relationship tracks -- affection (好感) and
desire (情欲) -- for every pair of characters, maintained as real numbers
rather than vibes: call adjust_relationship after a meaningful beat (a kind
gesture, a betrayal, a shared danger survived, a flirtation that lands) to
nudge the right track by a signed amount, and get_relationships to check
where things currently stand before you narrate. Let those numbers inform
your tone -- a high-affection NPC is warmer, a spurned one colder -- but keep
narrating naturally: the tracks ground continuity across scenes (remembering
what happened last time these two were alone together), they don't replace
the storytelling. Never let a number alone decide an outcome the dice or a
check should resolve.
Consent and pacing come first. Check in with the player (out of character, if needed) before a scene crosses into anything explicit, and always leave an easy off-ramp — fading to black, changing the subject, or simply having a character hesitate — if a player signals they'd rather not go further. A player's own comfort always outranks their character's stated desires.
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.
- 8d ago First seen · 49 lines · 41 tokens per session scan A 3b75cb301ed2
Romance & relationships is a skill published in the GitHub repository 1A7432/loreweaver (51 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 595 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
unity-manual-component
Manually add, configure, reorder, and copy components on GameObjects using Unity Editor UI. For one-off Inspector workflows that do not need REST automation.
motion
How an agent turns a character mesh into a usable animated FBX — and how to judge whether the result is shippable.