SMT packages library in eagle
Many of the generic packages I have used with Eagle are in my "package" library, which should be (I think) included in the Eagle Tools release at http://www.embedinc.com/pic/dload.htm.

However, if you need a package, the safest and usually simplest option is to just make it yourself.  What's the big deal?  By the time you typed a question here and get a answer, you would be done if you spent the time making it yourself.

Added in response to comment

No, there are many more than 2 packages in my Eagle package library.  I just looked, and there are only 2 devices in there, TQFP64 and TQFP80.  I forget why I made those, but there must have been some special purpose at the time.  In any case, you asked about packages, not devices, so I don't see why you care about these two devices.

The point to creating your own, and the reason I always do it, is that it would take more time to vet and possibly modify someone else's package than to simply create my own.  Or put another way, defining is easier than detailed checking.  Also, others aren't going to create packages with my conventions for the tPlace, tValue, tName, and tDocu layers and other details.

Spending 5 minutes making a package is better than spending 10 minutes checking someone else's package, finding things that I need to change, and then making the changes.