How do I install the Hts Evm Hybrid skill?

Run npx skillmds@latest add evaluris-solutions/hts-evm-hybrid in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Hts Evm Hybrid safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Hts Evm Hybrid?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Hts Evm Hybrid free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Hts Evm Hybrid?

Evaluris-Solutions (@evaluris-solutions) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Hts Evm Hybrid by evaluris-solutions

Name: Hts Evm Hybrid
Rating: 4.666666666666667 (3 reviews)
Author: Evaluris-Solutions

Hts Evm Hybrid

Call Hedera Token Service from Solidity via HTS system contract at 0x167 — associate, mint, transfer HTS tokens inside contracts, differences vs ERC-20 facade on HTS tokens, reentrancy considerations for precompile calls, 2023 HTS allowance exploit lessons. Use when user mentions HTS precompile, IHederaTokenService, associateToken Solidity, HTS from contract, reentrancy Hedera precompile, Uniswap-style hooks on Hedera.

File contents

Overview

HTS exposes a system contract at address 0x0000000000000000000000000000000000000167 implementing IHederaTokenService functions callable from user contracts (HTS system contract).

When to use this skill

Orchestrating HTS mint/associate/transfer inside contract logic.
Auditing hook/reentrancy interactions introduced by HIP-1195-style allowance behaviors.

Prerequisites

Working Hardhat → Hashio setup (hedera-smart-contract-evm).
Correct conversion between token ID / account ID and EVM address representations — validate utilities before production.

Workflow

Import official interface ABI from Hashgraph samples or vendor packages — demo uses contracts/IHederaTokenServiceMinimal.sol.
Route calls through address HederaPrecompileAddresses.HTS.
Decode response codes — success vs failure enums differ from raw require checks; production code must branch on returned int64.
Reentrancy — external calls to HTS may invoke token hooks; treat like external calls in Checks-Effects-Interactions ordering.
Security history — read references/precompile-vuln-taxonomy.md for classes of failures including the 2023 HTS allowance incident.

Deploy demo: scripts/precompile-deploy.cjs.

Examples

Example 1

“Associate my contract’s callers with token X.”

Usually wrong pattern — association targets accounts, not transient callers; prefer explicit associate flows.

Example 2

“Mint inside contract after deposit.”

Ensure supplyKey authorizations align with contract-controlled keys or delegated signatures.

Example 3

“Why did ERC-20 transfer behave differently than HTS?”

ERC-20 facade paths still obey HTS association/KYC rules under the hood.

Troubleshooting

Issue	Tip
`INVALID_TOKEN_ID`	Address conversion incorrect
Unexpected hook recursion	Audit HIP-1195 interactions

References

Local: references/precompile-addresses.md, references/precompile-vuln-taxonomy.md, references/solidity-htst-examples.md

---name: hts-evm-hybriddescription: Call Hedera Token Service from Solidity via HTS system contract at 0x167 — associate, mint, transfer HTS tokens inside contracts, differences vs ERC-20 facade on HTS tokens, reentrancy considerations for precompile calls, 2023 HTS allowance exploit lessons. Use when user mentions HTS precompile, IHederaTokenService, associateToken Solidity, HTS from contract, reentrancy Hedera precompile, Uniswap-style hooks on Hedera.---## OverviewHTS exposes a **system contract** at address `0x0000000000000000000000000000000000000167` implementing `IHederaTokenService` functions callable from user contracts ([HTS system contract](https://docs.hedera.com/hedera/core-concepts/smart-contracts/tokens-managed-by-smart-contracts/hedera-token-service-system-contract.md)).## When to use this skill- Orchestrating HTS mint/associate/transfer inside contract logic.- Auditing **hook/reentrancy** interactions introduced by HIP-1195-style allowance behaviors.## Prerequisites- Working Hardhat → Hashio setup (`hedera-smart-contract-evm`).- Correct conversion between **token ID** / **account ID** and **EVM address** representations — validate utilities before production.## Workflow1. Import official interface ABI from Hashgraph samples or vendor packages — demo uses [contracts/IHederaTokenServiceMinimal.sol](contracts/IHederaTokenServiceMinimal.sol).2. Route calls through address `HederaPrecompileAddresses.HTS`.3. Decode **response codes** — success vs failure enums differ from raw `require` checks; production code must branch on returned `int64`.4. **Reentrancy** — external calls to HTS may invoke token hooks; treat like external calls in Checks-Effects-Interactions ordering.5. **Security history** — read [references/precompile-vuln-taxonomy.md](references/precompile-vuln-taxonomy.md) for classes of failures including the **2023 HTS allowance incident**.Deploy demo: [scripts/precompile-deploy.cjs](scripts/precompile-deploy.cjs).## Examples**Example 1**> “Associate my contract’s callers with token X.”Usually wrong pattern — association targets **accounts**, not transient callers; prefer explicit associate flows.**Example 2**> “Mint inside contract after deposit.”Ensure `supplyKey` authorizations align with contract-controlled keys or delegated signatures.**Example 3**> “Why did ERC-20 transfer behave differently than HTS?”ERC-20 facade paths still obey HTS association/KYC rules under the hood.## Troubleshooting| Issue | Tip || --- | --- || `INVALID_TOKEN_ID` | Address conversion incorrect || Unexpected hook recursion | Audit HIP-1195 interactions |## References- Local: [references/precompile-addresses.md](references/precompile-addresses.md), [references/precompile-vuln-taxonomy.md](references/precompile-vuln-taxonomy.md), [references/solidity-htst-examples.md](references/solidity-htst-examples.md)

Frequently asked questions